[SERVER-15022] TO-shard fails to accept new chunk in inactive clusters after first reconfig Created: 25/Aug/14  Updated: 11/Jul/16  Resolved: 27/Aug/14

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

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

Issue Links:
Related
is related to SERVER-18096 Shard primary incorrectly reuses clos... Closed
Operating System: ALL
Participants:

 Description   

The TO-shard of a migration depends on the FROM-shard to provide sharding details in the case that this is the first sharding operation to hit the TO-shard. If the TO-shard was previously initialized in any cluster, however (such as if the primary of the TO-shard was stepped-down and stepped-back-up) the TO-shard will not initialize with the cluster info sent by the FROM shard and cleanly fail to migrate (with a cryptic error message).



 Comments   
Comment by Githook User [ 26/Aug/14 ]

Author:

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

Message: SERVER-15022 don't rely on configServer.ok() for sharding state when recv'ing chunk

configServer global is not reset on replica set stepdown
Also better error messages when sharding state not enabled.
Branch: master
https://github.com/mongodb/mongo/commit/0f0e24f5dce718bd1d54f7ca3762d3f4cb13db2f

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