-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
v8.2, v8.0, v7.0
-
Repl 2025-11-24
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
prepared_transaction_kill_during_step_up_refresh.js can fail with "commitTransaction for a prepared transaction cannot be run before its prepare oplog entry has been majority committed" when running commitTransaction on the new primary after previously preparing a transaction on the former primary. Even though the prepareTransaction runs with wc: majority, this only ensures that the original primary's commit point contains it. Since we step up a new primary in the middle of this transaction, it's possible that the commit point did not propagate while it was a secondary. This means that the new primary needs a chance to advance its commit point to include the prepareTimestamp before we can complete the transaction with commitTransaction.
- is related to
-
SERVER-114295 api_version_prepare_txn.js should wait for lastCommitted to advance on stepped up secondary
-
- Closed
-
- related to
-
SERVER-114295 api_version_prepare_txn.js should wait for lastCommitted to advance on stepped up secondary
-
- Closed
-