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

Add retry to continuous config primary step-down thread when primary steps down and closes all connections

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.5, 3.3.3
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Sprint:
      Sharding 11 (03/11/16)
    • Linked BF Score:
      0

      Description

      The continuous config primary step down thread first tries to contact a config server. The C++ code that is eventually called opens a connection to the specified config server, and follows up with an isMaster command. However, the config server, if a primary, may step down between creating the connection and calling isMaster. When the primary steps down it closes all of its connections, so the followup isMaster command throws an error.

      In this case, the error should be caught and the command retried, rather than quitting with an error.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: