-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2
-
Repl 2020-06-15
-
11
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Step-up can run further operations on the same operation context, which will be left with session metadata (lsid, txnNumber, etc.) from the last transaction the node aborted as part of step-up.
These operations can then invariant that the session is not checked out even though they have session metadata on their operation context. Ordinarily they would exit early for not having a stmtId here. That stmtId is assigned here from the update request, which comes from here. That would return an uninitialized stmtId, except the txnNumber is not null like it should be here.
- causes
-
SERVER-48729 Don't duplicate maxNumberOfTransactionOperationsInSingleOplogEntry parameter in refine_collection_shard_key_abort_on_stepup.js
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-49459 Check sticky state on OperationContext and consider fixing
-
- Closed
-