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

Odd connection timeouts and rejections when replicaset secondary is lagged

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.2.8
    • Fix Version/s: None
    • Component/s: Networking, Stability
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      The scenarios used to make this happen are not easily reproducible. Our setup is a 3 member replicaset in which one of them becomes angry enough to start closing connections.

      Show
      The scenarios used to make this happen are not easily reproducible. Our setup is a 3 member replicaset in which one of them becomes angry enough to start closing connections.

      Description

      We were performing a rather massive set of updates. During these updates, one of the secondaries began to show SEND_ERROR messages in the logs, and also began to lag behind the primary. The CSHARP client was not catching the errors, causing everything to be inoperable from a client standpoint.

      The only values that show up in the logfiles are:
      2016-08-17T10:53:57.994-0500 I NETWORK [conn886174] SocketException handling request, closing client connection: 9001 socket exception [SEND_ERROR] server [webserver:55640]

      – I will also file a report on this with the CSHARP crew, as it appears to be unhandled coming back to the client.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kelsey.schubert Kelsey T Schubert
              Reporter:
              sallgeud Chad Kreimendahl
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: