[KUDU-2343] Java client doesn't properly reconnect to leader master when old leader is online

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.3.0, 1.3.1, 1.4.0, 1.5.0, 1.6.0, 1.7.0
• Fix Version/s: 1.5.1, 1.7.0, 1.6.1, 1.8.0
• Component/s: client, java
• Target Version/s: 1.5.1, 1.7.0, 1.6.1, 1.8.0
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 13/Mar/18 18:36
• Updated: 10/Sep/18 14:50
• Resolved: 15/Mar/18 15:57

Description

In the following sequence of events, the Java client doesn't properly fail over to locate a new master, and in fact gets "stuck" until the client is restarted:

• client connects to the cluster and caches the master locations
• client opens a table and caches tablet locations
• the master fails over to a new leader
• the tablet either goes down or fails over, causing the client to need to update its tablet locations

In this case, it gets stuck in a retry loop where it will never be able to connect to the new leader master.