[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. |
| 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: |