[SERVER-28643] Propagate readConcern::afterClusterTime from client to mongos to mongod Created: 05/Apr/17  Updated: 29/Jan/18  Resolved: 02/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: Needs Triage
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Mathias Stearn
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently readConcern is carried by the ServerSelectionMetadata and as it gets rebuilt it may lose afterClusterTime argument that will affect causalConsistency.
The fix need to ensure that the afterClusterTime provided by the client gets propagated all the way to mongod.



 Comments   
Comment by Misha Tyulenev [ 02/Oct/17 ]

The current tests do the equivalent coverage.

Comment by Ramon Fernandez Marina [ 24/Aug/17 ]

Author:

{'username': u'samantharitter', 'name': u'samantharitter', 'email': u'samantha.ritter@10gen.com'}

Message:SERVER-28643 Do not rely on __cplusplus value for inclusion of void_t
Branch:master
https://github.com/mongodb/mongo/commit/276008e5496427cf9c3b18d4c01b73e064e37004

Generated at Thu Feb 08 04:18:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.