-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying
-
Fully Compatible
-
Query 2020-05-18, Query 2020-06-01, Query 2020-06-15
SERVER-37364 makes the transaction coordinator return the decision as soon as the decision is made durable. This has caused report_post_batch_resume_token.js (when run in change_streams_sharded_collections_passthrough suites) to fail the check that the changestream cursor gets back two transaction events in the response to the first getMore after commitTransaction returns. It turns out that waiting for the inserts to be majority committed does not make this check pass reliably. This test may need to be rewritten for it to work with a sharded cluster.
- is related to
-
SERVER-37364 Coordinator should return the decision to the client as soon as the decision is durable
- Closed
- related to
-
SERVER-49423 Do not set coordinateCommitReturnImmediatelyAfterPersistingDecision in change stream multiversion suites
- Closed