[SERVER-4604] inserts need better handling of version changes Created: 03/Jan/12  Updated: 11/Jul/16  Resolved: 05/Jan/12

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

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Greg Studer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File insert_during_migrate.js    
Issue Links:
Depends
Duplicate
is duplicated by SERVER-6781 Document in the wrong shard. Closed
Related
is related to SERVER-5200 slowNightly tests failing on sharding... Closed
is related to SERVER-5749 updates need better handling of versi... Closed
Operating System: ALL
Participants:

 Description   

In at least certain cases, inserts do not re-check the shard they were sent to when receiving a bad version in checkShardVersion. This can lead to misdirected inserts if migrations are heavy, particularly if migrations are taking a lot of resources. (this, along with SERVER-4603, may be impacting mrShardedOutput.js/bigMapReduce.js).

Solution - probably refactor this code in line with the new pcursor stuff.



 Comments   
Comment by auto [ 05/Jan/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4604 handle sharded bulk insert in a safer way

also first step of getting all-inclusive sharded insert method
Branch: master
https://github.com/mongodb/mongo/commit/2767d9794505cd3fbdbec28a2610b3157ed9fd40

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