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: add support for initialize-target-sequences in MoveTables SwitchTraffic --tablet-types PRIMARY --dry-run mode #17831

Open
mcrauwel opened this issue Feb 20, 2025 · 0 comments · May be fixed by #17842

Comments

@mcrauwel
Copy link
Contributor

Feature Description

We have support to initialize the target sequences during the swtiching of PRIMARY (write) traffic. But in dry run mode these commands seem not to be executed.

2 reasons why I believe this would be useful:

  1. I've run into a situation where the initialize-target-sequences took longer than the allowed time (default 15sec) and the SwitchTraffic failed because of this. This wasn't caught in dry-run mode.
  2. While dry-run would execute all the steps to check the sequences verify the work it would need to do to figure out if updates are needed (just not the actual updating), we could use the dry-run output as some sort of a fail-safe mechanism in specific use-cases where initialize-target-sequences might not be 100% safe to execute (think busy systems with multi-tenant migrations running)

Use Case(s)

see description

@mcrauwel mcrauwel added the Needs Triage This issue needs to be correctly labelled and triaged label Feb 20, 2025
@mattlord mattlord added Type: Feature Component: VReplication and removed Needs Triage This issue needs to be correctly labelled and triaged labels Feb 20, 2025
@github-project-automation github-project-automation bot moved this to Backlog in VReplication Feb 20, 2025
@rohit-nayak-ps rohit-nayak-ps self-assigned this Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

3 participants