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

Replication code does not retry interrupted system call

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-rc6
    • Fix Version/s: 3.0.0-rc9, 3.1.0
    • Component/s: Networking, Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:

      Description

      While debugging an issue involving a replica set using gdb got the following error:

      2015-01-25T16:10:05.936-0500 W NETWORK  [ReplExecNetThread-0] Failed to connect to 127.0.0.1:27117, reason: errno:4 Interrupted system call
      2015-01-25T16:10:05.936-0500 I REPL     [ReplicationExecutor] Error in heartbeat request to localhost:27117; Location18915 Failed attempt to connect to localhost:27117; couldn't connect to server localhost:27117 (127.0.0.1), connection attempt failed
      2015-01-25T16:10:05.936-0500 I REPL     [ReplicationExecutor] can't see a majority of the set, relinquishing primary
      2015-01-25T16:10:05.936-0500 I REPL     [ReplicationExecutor] Stepping down from primary in response to heartbeat
      2015-01-25T16:10:05.936-0500 I REPL     [replCallbackWithGlobalLock-0] transition to SECONDARY

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: