[SERVER-40060] Retry replSetInitiate in ReplSetTest fixture Created: 10/Mar/19  Updated: 29/Oct/23  Resolved: 17/Mar/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.10

Type: Improvement Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
causes SERVER-40307 ssl_cluster_ca.js and ssl_hostname_va... Closed
Related
related to SERVER-49305 Remove reconfig retries in our tests Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-03-25
Participants:
Linked BF Score: 8

 Description   

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.



 Comments   
Comment by Githook User [ 17/Mar/19 ]

Author:

{'email': 'jesse@mongodb.com', 'name': 'A. Jesse Jiryu Davis', 'username': 'ajdavis'}

Message: SERVER-40060 Add retry in ReplSetTest.initiate
Branch: master
https://github.com/mongodb/mongo/commit/58ff5248610305a35403020077a4dbdcd0691ff0

Generated at Thu Feb 08 04:53:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.