[SERVER-4606] need to restart mongos after adding shard Created: 03/Jan/12 Updated: 15/Aug/12 Resolved: 22/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
In some cases, it seems mongos must be restarted after adding a shard for mongos to pick up the changes. Logs at: |
| Comments |
| Comment by Spencer Brody (Inactive) [ 22/May/12 ] |
|
This is most likely a duplicate of |
| Comment by Spencer Brody (Inactive) [ 20/Apr/12 ] |
|
Okay thanks - let me ask you a few questions to gather information to help us diagnose: Can you tell us the exact sequence of events that caused this to happen? Did you have any failed addShard attempts first? |
| Comment by Alex Smith [ 20/Apr/12 ] |
|
Confirmed as persisting in 2.0.3. Restarting mongos allowed me to add the new shard. |
| Comment by Greg Studer [ 29/Jan/12 ] |
|
According to groups, this sequence may reproduce / fix (on 2.0.2): just happened to us as well. mongos refused addShard with a replica set consisting of 2 nodes and what we did to resolve this issue: |
| Comment by Greg Studer [ 19/Jan/12 ] |
|
See http://groups.google.com/group/mongodb-user/browse_thread/thread/7d2b1e3e79a745ff for context. |