You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: