[SERVER-4476] mongod's cached data should be refreshed on removeShard Created: 12/Dec/11  Updated: 11/Jul/16  Resolved: 11/Jun/12

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

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   

mongod's data isn't necessarily flushed when a shard is removed - this can lead to inconsistency in shard naming.

fastest fix is probably explicitly to reload shard info prior to migrate.



 Comments   
Comment by auto [ 11/Jun/12 ]

Author:

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

Message: SERVER-4476 fix unrelated issue that breaks test, make zero-version config reloads work

in specific cases, mongod can fail to reload its ShardChunkManager without this change
Branch: master
https://github.com/mongodb/mongo/commit/701df8345f2f7bdf254c56f6f490df787ac03752

Comment by auto [ 11/Jun/12 ]

Author:

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

Message: SERVER-4476 reload shard data before migration starts
Branch: master
https://github.com/mongodb/mongo/commit/11da8181ead847d3a48e7953a18bdb4e1f347ae9

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