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 was noticed that if VTOrc is running with the --change-tablets-with-errant-gtid-to-drained flag, then after it converts a tablet that has an errant GTID to a drained type, it forgets them! This leads to the metric of ErrantGTIDTabletCount to be incorrect, since VTOrc removed the tablet that had the errant GTID from its list of tablets! That metric then always reports a value of 0 which is incorrect since we have errant GTIDs that need to be looked at by the user.
Reproduction Steps
Run VTOrc with --change-tablets-with-errant-gtid-to-drained flag
Introduce an errant GTID on a replica.
Monitor the ErrantGTIDTabletCount gauge and see that it goes to 0 even without us fixing any errant GTID.
Binary Version
main
Operating System and Environment details
-
Log Fragments
No response
The text was updated successfully, but these errors were encountered:
Overview of the Issue
It was noticed that if VTOrc is running with the
--change-tablets-with-errant-gtid-to-drained
flag, then after it converts a tablet that has an errant GTID to a drained type, it forgets them! This leads to the metric ofErrantGTIDTabletCount
to be incorrect, since VTOrc removed the tablet that had the errant GTID from its list of tablets! That metric then always reports a value of 0 which is incorrect since we have errant GTIDs that need to be looked at by the user.Reproduction Steps
--change-tablets-with-errant-gtid-to-drained
flagErrantGTIDTabletCount
gauge and see that it goes to 0 even without us fixing any errant GTID.Binary Version
Operating System and Environment details
Log Fragments
No response
The text was updated successfully, but these errors were encountered: