[SERVER-20517] Queries failing when replica set secondary is down. Created: 21/Sep/15 Updated: 06/Apr/23 Resolved: 23/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Lowe | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian7 |
||
| Operating System: | Linux |
| Steps To Reproduce: | Stop secondary |
| Participants: |
| Description |
|
We have a sharded cluster, with mongos on each of the app servers. If I stop a secondary on the first shard, then from the replica set point of view, everything seems ok (primary still up). However, our application servers are then unable to query the local mongos (the queries just time out). Looking at the mongos logs, there are errors like this: W NETWORK [Balancer] Failed to connect to <IP of replica set SECONDARY>, reason: errno:111 Connection refused |
| Comments |
| Comment by Scott Lowe [ 23/Sep/15 ] |
|
Doh, someone had slipped a read preference in the app code. It's working as expected now. Thank you for your support, and sorry for the false issue. |
| Comment by Sam Kleinman (Inactive) [ 21/Sep/15 ] |
|
Thanks for this report, and sorry that you're experiencing this issue. I have a few questions about your configuration and system:
Regards, |