-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.1.10
-
Component/s: Replication
-
None
-
ALL
-
-
Repl 2019-05-20
-
10
Running a speculative majority read command that checks out the session (by, example, including a 'txnNumber') may hit this invariant when trying to read from the transactions table via DBDirectClient here, which may be called when we check out a session. We may be able to fix this by returning immediately inside waitForSpeculativeMajorityReadConcern if we are inside a direct client.
- duplicates
-
SERVER-41050 Ban txnNumbers outside of transactions and retryable writes
- Closed
- is related to
-
SERVER-40860 Including a "txnNumber" field on a command using "linearizable" read concern will bypass post-execution read concern wait
- Closed