[KUDU-2302] Leader crashes if it can't resolve DNS address of a peer

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.6.0, 1.7.0, 1.8.0, 1.7.1, 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.11.1, 1.13.0, 1.14.0
• Fix Version/s: 1.16.0
• Component/s: consensus, master, tserver
• Labels: crash roadmap-candidate stability
• Assignee: Andrew Wong
• Reporter: Todd Lipcon
• Created: 16/Feb/18 00:36
• Updated: 12/Jun/21 18:52
• Resolved: 12/Jun/21 18:52

Description

In BecomeLeader we call:

 CHECK_OK(BecomeLeaderUnlocked());

This will fail if it fails to resolve the address of one of its peers. Instead it should probably continue to be leader but consider attempts to RPC to that peer to be failed due to network resolution (with periodic retries of resolution)

Issue Links

• is duplicated by: KUDU-3278 DNS entry removal of a tablet server causes one of its peers to crash
• relates to: KUDU-1099 Consensus should be more resilient to transient DNS failures