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: Refactor how VTOrc starts up #15314

Closed
GuptaManan100 opened this issue Feb 21, 2024 · 0 comments · Fixed by #15315
Closed

Feature Request: Refactor how VTOrc starts up #15314

GuptaManan100 opened this issue Feb 21, 2024 · 0 comments · Fixed by #15315
Labels
Component: VTorc Vitess Orchestrator integration Type: Feature Request

Comments

@GuptaManan100
Copy link
Member

Feature Description

Orchestrator used to rely on crawling the MySQL replication graph to figure out all the nodes in the cluster. This meant that it needed some time to setup before it could run any recoveries. VTOrc on the other hand has all the node information available in the topo-server.

It doesn't look like VTOrc requires the wait period that it currently has. Right now VTOrc waits for 3 times the --instance-poll-time duration before running any repairs, but that seems wasteful.

Use Case(s)

Faster setup and recoveries from VTOrc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: VTorc Vitess Orchestrator integration Type: Feature Request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant