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.

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

Feature Request: support an --all-cells option in MoveTables #13078

Closed
maxenglander opened this issue May 12, 2023 · 0 comments · Fixed by #14341
Closed

Feature Request: support an --all-cells option in MoveTables #13078

maxenglander opened this issue May 12, 2023 · 0 comments · Fixed by #14341
Assignees

Comments

@maxenglander
Copy link
Collaborator

Feature Description

When --all-cells is specified in MoveTables, find available cells in the source keyspace and use those to replicate from.

Return an error if both --cells and --all-cells are specified.

Use Case(s)

My team and I run MoveTables several times per month on large source keyspaces in multi-cell environments. 99% of the time we specify all available cells in the source keyspace. If we forget to do this (happens from time to time), a single cell is automatically selected by MoveTables.

If part way through the MoveTables process, a PlannedReparentShard occurs (happens automatically in our environment), it can break the MoveTables workflow.

If --all-cells was a supported option, it would make our lives a little bit easier.

@maxenglander maxenglander added Type: Feature Needs Triage This issue needs to be correctly labelled and triaged labels May 12, 2023
@mattlord mattlord removed the Needs Triage This issue needs to be correctly labelled and triaged label May 12, 2023
@mattlord mattlord self-assigned this May 12, 2023
@mattlord mattlord added this to v17.0.0 May 12, 2023
@frouioui frouioui added this to v18.0.0 Jun 30, 2023
@frouioui frouioui moved this to Backlog in v18.0.0 Jun 30, 2023
@frouioui frouioui removed this from v17.0.0 Jun 30, 2023
@github-project-automation github-project-automation bot moved this from Backlog to Done in v18.0.0 Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants