-
Type: Bug
-
Resolution: Fixed
-
Priority: Critical - P2
-
Affects Version/s: 5.2.0, 6.0.0, 6.1.0, 6.2.0-rc4
-
Component/s: None
-
Replication
-
Fully Compatible
-
ALL
-
v6.2, v6.0
-
Repl 2023-01-09
We install a callback inside the storage engine to determine how much oplog to keep for uncommitted transactions.
Upon completion, FCBIS reconstructs a new storage engine, but it does not re-instantiate this callback. When this callback is not present, we default to not truncating the oplog.
As a result, we will never truncate the oplog after completing a FCBIS. Restarting the node fixes this problem permanently.
- is related to
-
SERVER-72423 FCBIS will never delete drop-pending tables
- Closed
- related to
-
SERVER-72525 Randomly choose between FCBIS and logical initial sync every time in our testing
- Open