[SERVER-2082] mongos fails with "remotes don't match" Created: 09/Nov/10 Updated: 12/Jul/16 Resolved: 09/Nov/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | 1.7.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Luke Ehresman | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
two shards, each composed of two replicas (4 servers total). mongos is running on a separate box. all boxes are running Ubuntu Linux. |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Last night, my mongos died with this message. Tue Nov 9 03:34:22 [conn5875028] uncaught exception (remotes don't match old [10.4.1.7:51675] new [10.4.1.8:51675])(mongo::UserException) in PortMessageServer::threadRun, closing connection Those IPs are to two servers that do heavy writes to the system. I noticed it first thing this morning and restarted mongos. It came back online without any problem. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 09/Nov/10 ] |
|
the 1.7 nightly should fix this |