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

Set a smaller connection timeout for _await_cmd_all_nodes

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.3 Required
    • Component/s: Replication
    • None
    • ALL
    • v4.2, v4.0, v3.6
    • Repl 2019-07-01
    • 20

      The problem was that the timeout for get_primary() is 30s and that the connection timeout for mongo_client is also default to 30s for the test. So if it blocks on connecting to a node, the loop of finding the primary is also stuck. And so it times out first before being able to check isMaster on all nodes. I think we should set a smaller connection timeout (timeout_millis) when looping through all the nodes so we don't wait on a bad node forever.

            Assignee:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: