[SERVER-7833] mongos need restart after rs.remove Created: 04/Dec/12 Updated: 15/Feb/13 Resolved: 12/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christian Schellschmidt | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
when we remove a replica vom a sharded replica set, then the mongos hang up and need restart to work properly. command failed [getlasterror]: { "serverUsed" : "localhost/127.0.0.1:27017" , "ok" : 0.0 , "errmsg" : "could not get last error from sha Is thrown from the application. |
| Comments |
| Comment by Randolph Tan [ 12/Feb/13 ] |
|
Hi, The error is caused by the primary closing all connections when a replica set configuration change occurs. This is how it was currently designed, but we are also making changes such that it will not happen in most cases. You can check the progress on Thanks! |