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

Too many open connections kills primary but doesn't trigger failover

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • 2.0.5
    • None
    • Replication
    • None
    • ALL
    • Service Arch 2018-11-05, Service Arch 2018-11-19, Service Arch 2018-12-03, Service Arch 2018-12-17

    Description

      Late last night we had some issues with mongos (unfortunately not clear what went wrong - bouncing fixed it). About an hour later we then had a massive spike in the number of connections from mongos to the primary. This then caused 'too many open connections' to start flooding the primaries logs and connection attempts throughout our application to consistently fail. In effect, our primary was dead.

      However, our primary was still telling all the secondaries that it was alive and well so no failover happened.

      I think the health checks need to do more than they do. The primary can't just be "alive" it must be "alive and well" - i.e. responding to queries and new connections.

      Attachments

        Issue Links

          Activity

            People

              ben.caimano@mongodb.com Benjamin Caimano (Inactive)
              colinhowe Colin Howe
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: