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
It turns out that schema tracking is creating errant GTIDs that then prevent us from performing replication related operations like ResetReplication and WaitForPosition.
clusterInstance.VtTabletExtraArgs = []string{
"-lock_tables_timeout", "5s",
"-enable_semi_sync",
"-track_schema_versions=false", // remove this line once https://github.com/vitessio/vitess/issues/6474 is fixed
}
Once #6474 is fixed, the option line should be removed so that we can verify that schema tracking works well even when we reparent.
The text was updated successfully, but these errors were encountered:
There are a bunch of failures in this GH action run: https://github.com/vitessio/vitess/runs/1098675951
It turns out that schema tracking is creating errant GTIDs that then prevent us from performing replication related operations like
ResetReplication
andWaitForPosition
.To work around this temporarily, the fix is to disable schema tracking in https://github.com/vitessio/vitess/blob/master/go/test/endtoend/reparent/main_test.go like this:
Once #6474 is fixed, the option line should be removed so that we can verify that schema tracking works well even when we reparent.
The text was updated successfully, but these errors were encountered: