[
https://issues.apache.org/jira/browse/KUDU-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397861#comment-16397861
]
Alexey Serbin commented on KUDU-2343:
-------------------------------------
I think 1.3.0 is also affected, right?
> Java client doesn't properly reconnect to leader master when old leader is
> online
> ---------------------------------------------------------------------------------
>
> Key: KUDU-2343
> URL: https://issues.apache.org/jira/browse/KUDU-2343
> Project: Kudu
> Issue Type: Bug
> Components: client, java
> Affects Versions: 1.3.1, 1.4.0, 1.5.0, 1.6.0, 1.7.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
