[SERVER-4388] newly sharded collection requires config info reload on the mongod Created: 29/Nov/11  Updated: 11/Jul/16  Resolved: 29/Mar/12

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.1.0
Fix Version/s: 2.0.5, 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 mongos_no_detect_sharding.js    
Issue Links:
Depends
Duplicate
is duplicated by SERVER-4219 When a collection is sharded, mongods... Closed
Operating System: ALL
Participants:

 Description   

If we shard a collection with one mongos, the mongod will not know about the change until a setShardVersion command comes in. Since other mongoses do not know about the change, they may never send another setShardVersion command if they don't re-establish connections.

This can cause mongoses not to split, if the shard command comes from one mongos which then is not used to insert the data.



 Comments   
Comment by auto [ 19/Apr/12 ]

Author:

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

Message: SERVER-4388 update version of newly sharded collection on mongod primary after first sharding
Branch: v2.0
https://github.com/mongodb/mongo/commit/df84cb315987723fc3faff5cdd17dc46a6ca778a

Comment by auto [ 12/Dec/11 ]

Author:

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

Message: SERVER-4388 update version of newly sharded collection on mongod primary after first sharding
Branch: master
https://github.com/mongodb/mongo/commit/9d9b2cf71ae14f0813c1c587dfb8c21046d45234

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