[SERVER-4214] multiple connections to shards can rarely get mutually inconsistent versions when migrate occurs Created: 04/Nov/11  Updated: 08/Nov/11  Resolved: 08/Nov/11

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Eliot Horowitz (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mr_output_that_fails.txt    
Operating System: ALL
Participants:

 Description   

...think this has to do with migration triggered from the same mongos, so version is auto-reloaded afterward.

Sample bigMapReduce.js that fails - one of the connections has a stale version compared to the current version.



 Comments   
Comment by Ian Whalen (Inactive) [ 08/Nov/11 ]

Duplicate of SERVER-4215.

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