[SERVER-11843] Removal of replica-set members doesn't work for sharded DB when configServers are down Created: 25/Nov/13 Updated: 16/Dec/13 Resolved: 16/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Krishnachaitanya Thummuru | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS |
||
| Attachments: |
|
| Operating System: | Linux |
| Steps To Reproduce: | Provided in description summary |
| Participants: |
| Description |
|
We have Geo-redundancy setup for sharded database with below Configuration: Site-1 Shard#1 - set01 - (Host1: member#1- Primary DB, Host2:member#2- Secondary DB) Host7: Config Server1 Site-2 Issue: |
| Comments |
| Comment by Krishnachaitanya Thummuru [ 16/Dec/13 ] |
|
Thanks Stephen |
| Comment by Stennie Steneker (Inactive) [ 16/Dec/13 ] |
|
Hi Krishnachaitanya, Please be advised that I'm closing this issue due to inactivity. As per Scott's earlier replies, it is expected that the sharding metadata on the config servers will not be updated if 1 or more config servers are not available. If there are any specific errors to investigate we would need answers to the additional questions posed. Thanks, |
| Comment by Scott Hernandez (Inactive) [ 25/Nov/13 ] |
|
Please include answers to the following info:
|
| Comment by Krishnachaitanya Thummuru [ 25/Nov/13 ] |
|
Attached mongos log for your analysis. |
| Comment by Krishnachaitanya Thummuru [ 25/Nov/13 ] |
|
Hi Scott, Thanks for update. |
| Comment by Scott Hernandez (Inactive) [ 25/Nov/13 ] |
|
The members list for each shard in sh.status is just the seed list, so as long as one of those members is still valid then each mongos will discover and use the correct (and up) members. By definition no writes to the config servers for shard metadata can be done if not all of them are online. When all the config servers are back online the shard member list will be updated automatically. If you are seeing any errors please upload the logs where those errors occur. |