[SERVER-4603] when migrating the last chunk off of a shard for a collection, version set to 0 and does *not* block version reset 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.0.6, 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

Operating System: ALL
Participants:

 Description   

... this can lead to data written, then removed.



 Comments   
Comment by auto [ 10/May/12 ]

Author:

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

Message: SERVER-4603 handle last shard migration more correctly

Signed-off-by: Eric Milkie <milkie@10gen.com>
Branch: v2.0
https://github.com/mongodb/mongo/commit/dd21525b0210951619935e0c8964158c12cfe70f

Comment by auto [ 05/Jan/12 ]

Author:

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

Message: SERVER-4603 handle last shard migration more correctly
Branch: master
https://github.com/mongodb/mongo/commit/7e3bb61f7dfeca047fb23b7570941b2f26a3d988

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