Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
Description:
We will no longer support 'atClusterTime' with enableMajorityReadConcern:false. The external-facing implication of this is that:
- in 4.2 with enableMajorityReadConcern:false, we will not support transactions in sharded clusters with readConcern level 'snapshot'.
Done as part of earlier ticket. but need to update error message
- (Note that 4.0 does not support transactions in sharded clusters at all, and 4.2 with enableMajorityReadConcern:false only supports single-shard transactions.)
Done as part of earlier ticket.
- 4.0 users should be cautioned that if they are using enableMajorityReadConcern:false and single replica set transactions, then they may wish to avoid readConcern level 'snapshot' if they may transition to using a sharded cluster in 4.2, since this will break their application.
- In 4.2 with enableMajorityReadConcern:false, single-shard transactions will support readConcern levels 'local' and 'majority'.
Engineering Ticket Description:
This means that single-shard transactions on enableMajorityReadConcern:false shards cannot be run with readConcern level snapshot.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-39418 Ban atClusterTime with enableMajorityReadConcern:false
-
- Closed
-
- is related to
-
DOCS-12523 4.2: transactions supported on sharded clusters (part 1 March 14)
-
- Closed
-