Feature Description
In older versions of vitess there exists an undocumented vtctlclient sub command for MoveTables called GetState.
This prints out the current SwitchTraffic state for a MoveTables workflow. An example of what it looks like below:
MoveTables GetState keyspace.workflow
Reads Not Switched. Writes Not Switched
After talking with @mattlord it sounds like this sub-command won't be available in the current v19 vtctldclient version of MoveTables. Matt asked that I add this issue so he can look at options for bringing this functionality forward.
We discussed including the SwitchTraffic state as part of the status sub command for MoveTables.
Use Case(s)
I work with a lot of MoveTables across many different Vitess Clusters. So I frequently use GetState to remind me what the current state of a MoveTables workflow is before I take any action against the cluster. You could use the routing rules or possibly dry-run of SwitchTraffic/ReverseTraffic to obtain this information but I like how it is simple and has easy to read output.
Feature Description
In older versions of vitess there exists an undocumented vtctlclient sub command for
MoveTablescalledGetState.This prints out the current
SwitchTrafficstate for aMoveTablesworkflow. An example of what it looks like below:After talking with @mattlord it sounds like this sub-command won't be available in the current v19 vtctldclient version of MoveTables. Matt asked that I add this issue so he can look at options for bringing this functionality forward.
We discussed including the SwitchTraffic state as part of the
statussub command for MoveTables.Use Case(s)
I work with a lot of
MoveTablesacross many different Vitess Clusters. So I frequently useGetStateto remind me what the current state of aMoveTablesworkflow is before I take any action against the cluster. You could use the routing rules or possibly dry-run ofSwitchTraffic/ReverseTrafficto obtain this information but I like how it is simple and has easy to read output.