[SERVER-5749] updates need better handling of version changes (sharding_balance4.js failure) Created: 02/May/12  Updated: 15/Aug/12  Resolved: 02/May/12

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: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-5200 slowNightly tests failing on sharding... Closed
is duplicated by SERVER-5207 possible for writes/updates miss conf... Closed
Related
related to SERVER-4604 inserts need better handling of versi... Closed
Operating System: ALL
Participants:

 Description   

Because the chunk manager used to determine the shard to send updates to is not necessarily the same as the chunk manager used to verify an up-to-date version for the shard connection used in an update, it's possible for the chunk manager to be changed in the meantime, resulting in an update being sent via an up-to-date connection to the wrong shard.

Problem and fix is essentially the same as for SERVER-4604, but for updates.

Manifests in http://buildbot.mongodb.org/builders/Linux%2064-bit%20DUR%20OFF/builds/1073/steps/test_1/logs/stdio/text


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