[
https://issues.apache.org/jira/browse/KUDU-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-2387.
------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed in commit ae98ccacc.
> exportAuthenticationCredentials does not retry connectToCluster
> ---------------------------------------------------------------
>
> Key: KUDU-2387
> URL: https://issues.apache.org/jira/browse/KUDU-2387
> Project: Kudu
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.0
> Reporter: Todd Lipcon
> Assignee: Adar Dembo
> Priority: Critical
> Fix For: 1.9.0
>
>
> TestSecurity has the following TODO:
> {code}
> // TODO(todd): it seems that exportAuthenticationCredentials() doesn't
> properly retry
> // in the case that there is no leader, even though
> NoLeaderFoundException is a RecoverableException.
> // So, we have to use a hack of calling listTabletServers, which _does_
> properly retry,
> // in order to wait for the masters to elect a leader.
> {code}
> It seems like this causes occasional failures of tests like KuduRDDTest -- I
> saw a case where the client failed to connect due to a negotiation timeout,
> and then didn't retry at all. It's not clear why the 3-second negotiation
> timeout was insufficient in this test case but likely just machine load or
> somesuch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
