-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
-
Repl 2019-02-11
-
7
If we recalculate the stable timestamp after we commit the transaction, write the commit oplog entry, and update the metrics, but before we close the oplog hole, then we may never recalculate it after the oplog hole actually closes.
This does not go away when we stop pinning the stable timestamp back. This is due to the OplogSlotReserver holding open an oplog hole past where we recalculate the stable timestamp.
- is related to
-
SERVER-38302 Committing or aborting prepared transactions may fail to un-pin stable timestamp
- Closed
-
SERVER-43978 Stable timestamp is not being recalculated after aborting oplog holes
- Closed