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

Configurable replSetReconfig isSelf socket timeouts

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication

      During testing we learned that a force replica set reconfig when nodes are down will take a substantially longer time to complete than first anticipated.

      We'd like to tune that 30 second value by making it configurable through the replSetReconfig command.

      In our uses, this command is run when we are certain the affected nodes are in a network partition, and timing out closer to 2-5 seconds is more reasonable. In large clusters, the 30second timeout could extend into several minutes (perhaps several tens of minutes in the case of clusters with lots of non-voting secondaries)

      Perhaps along side the maxTimeMs parameter, there could be a connectTimeoutMs parameter?

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            jack.wearden@mongodb.com Jack Wearden
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: