[SERVER-4997] Mongos not clearing stale connections Created: 17/Feb/12 Updated: 06/Apr/23 Resolved: 19/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Christian Tonhäuser | Assignee: | Unassigned |
| 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 |
|
We had the following issue on our production environment today: Due to a mistake, a mongod process needed to be restarted. This caused the secondary member of the replica set to failover to primary. From that point on, it was no longer possible to query a non-sharded DB that resides on the replica set that experienced the restart. [code] After manually retrying the query by repeating the command over and over (between 20-40 times) in mongo shell, the situation eventually cleared up and queries worked normally again, both from the shell as well as from our application. Unfortunately, this process needed to be repeated for every mongos-instance on the cluster, which is six in total. It looks to me as if mongos does not check connections to the cluster's other members before using them. Or is it already there and we just haven't seen the switch for it, yet? |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 19/Feb/12 ] |
|
An admin shouldn't have to cycle today - but you will get one error per connection. |