-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
Repl 2024-10-28, Repl 2024-11-11
It seems like lastAppliedOpTimeWaiterList and lastWriterOpTimeWaiterList use the same metric. These waiter lists are created with a reference to the metric, and then when we update the metric we just set it to the count to we want it to be, which I believe means that the two waiter lists are overriding the metric whenever they are updated, and it makes it confusing which waiter list this metric is referring to, and in t2 it means that any changes to the metric might be just a result of the metric getting overwritten by the other waiter list. We should separate out this metric.
We should also make sure that the definition in t2 is added correctly after this ticket.