[SERVER-18149] shard replaced, but change only picked up by 1 of 3 config servers Created: 21/Apr/15  Updated: 15/May/15  Resolved: 15/May/15

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

Type: Bug Priority: Minor - P4
Reporter: Annette Morrissey (Inactive) Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

A shard "r3" was replaced with a new server (same shard name). One mongos process recognised the change. The second and third mongos processes had a stale picture of which nodes made up rs3.
Once rs3 was re-added, the balancer (on one of the mongos nodes) started balancing to it's picture of "r3". Remaining two nodes kept looking for the old rs3.



 Comments   
Comment by Ramon Fernandez Marina [ 15/May/15 ]

Unfortunately there's not enough information here to determine if there is a bug in the server. Please feel free to reopen if more information can be gathered.

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