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

Retry replSetInitiate in ReplSetTest fixture

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2019-03-25
    • 8

      We've seen build failures where replSetInitiate failed: The node cannot resolve its own hostname in the list of members, and therefore fails the command thinking that the replica set config does not include itself. A typical log line is:

      [js_test:mixed_mode_sharded_transition_nossl] 2018-12-29T21:00:01.068+0000 c20022| 2018-12-29T21:00:01.068+0000 W NETWORK  [conn1] getaddrinfo("ip-10-122-5-158") failed: Temporary failure in name resolution 

      It might be worthwhile to retry "Temporary failure in name resolution" in the server code itself. Meanwhile, add a retry loop around replSetInitiate in replsettest.js, the same as the retry we added around replSetReconfig inĀ SERVER-27551.

            Assignee:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: