Odd connection timeouts and rejections when replicaset secondary is lagged

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.2.8
    • Component/s: Networking, Stability
    • None
    • ALL
    • 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.
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Kelsey Schubert
            Reporter:
            Chad Kreimendahl
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: