Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20517

Queries failing when replica set secondary is down.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 3.0.5
    • Sharding
    • None
    • Debian7
    • Linux
    • Hide

      Stop secondary
      Observer timing out queries, and errors in mongos logs.

      Show
      Stop secondary Observer timing out queries, and errors in mongos logs.

    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
      W NETWORK [ReplicaSetMonitorWatcher] Failed to connect to <IP of replica set SECONDARY>, reason: errno:111 Connection refused

      Attachments

        Activity

          People

            sam.kleinman Sam Kleinman (Inactive)
            bgsosh@gmail.com Scott Lowe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: