Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Job migrate - CH multishard/replica provision race condition #462

Open
guidoiaquinti opened this issue Jun 30, 2022 · 0 comments
Open

Job migrate - CH multishard/replica provision race condition #462

guidoiaquinti opened this issue Jun 30, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@guidoiaquinti
Copy link
Contributor

guidoiaquinti commented Jun 30, 2022 •
edited
Loading

Bug description

In a setup with an internal ClickHouse made by multiple shards/replicas, we should wait for all the nodes to be up and running before triggering the migration job. Otherwise it will fail (and likely succeeding during a retry)

Expected behavior

Migration job doesn't fail.

Actual behavior

Migration job often fails the first run.

How to reproduce

Execute the test_clickhouse_sharding.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@guidoiaquinti