[SERVER-29455] Mongos egress operations over DBClient must update OperationTimeTracker Created: 06/Jun/17  Updated: 29/Jan/18  Resolved: 17/Nov/17

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Misha Tyulenev
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29700 findAndModify returns operationTime b... Closed
Related
is related to SERVER-29456 Mongos should respond with cluster ti... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13, Sharding 2017-12-04
Participants:

 Description   

Currently this is done directly in ShardingTaskExecutor::scheduleRemoteCommand which isn't used by DBClient.



 Comments   
Comment by Kaloian Manassiev [ 30/Oct/17 ]

This makes map/reduce (which is the only thing which uses DBClient) not causally consistent and needs to be documented in the release notes.

misha.tyulenev, can you please work with the docs team?

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