You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 03:23:00 UTC
[jira] [Updated] (KUDU-2592) Java TestMasterFailover is flaky
[ https://issues.apache.org/jira/browse/KUDU-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-2592:
------------------------------
Component/s: test
> Java TestMasterFailover is flaky
> --------------------------------
>
> Key: KUDU-2592
> URL: https://issues.apache.org/jira/browse/KUDU-2592
> Project: Kudu
> Issue Type: Bug
> Components: test
> Affects Versions: 1.8.0
> Reporter: William Berkeley
> Priority: Major
> Attachments: TEST-org.apache.kudu.client.TestMasterFailover.xml
>
>
> The logs show a leader master is elected but the test still fails with:
> {noformat}
> 04:43:58.817 [ERROR - Test worker] (RetryRule.java:76) testKillLeaderBeforeCreateClient(org.apache.kudu.client.TestMasterFailover): failed run 1
> org.apache.kudu.client.NoLeaderFoundException: Master config (127.4.158.190:55468,127.4.158.188:46940,127.4.158.189:44906) has no leader.
> at org.apache.kudu.client.ConnectToCluster.incrementCountAndCheckExhausted(ConnectToCluster.java:279)
> at org.apache.kudu.client.ConnectToCluster.access$100(ConnectToCluster.java:47)
> at org.apache.kudu.client.ConnectToCluster$ConnectToMasterCB.call(ConnectToCluster.java:323)
> at org.apache.kudu.client.ConnectToCluster$ConnectToMasterCB.call(ConnectToCluster.java:312)
> at com.stumbleupon.async.Deferred.doCall(Deferred.java:1280)
> ...
> {noformat}
> Attaching logs from a failing run.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)