You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Burcu Ozkan (Jira)" <ji...@apache.org> on 2020/04/06 16:09:00 UTC

[jira] [Created] (RATIS-844) RaftClient should connect to the updated leader when the old leader is partitioned from the cluster

Burcu Ozkan created RATIS-844:
---------------------------------

             Summary: RaftClient should connect to the updated leader when the old leader is partitioned from the cluster
                 Key: RATIS-844
                 URL: https://issues.apache.org/jira/browse/RATIS-844
             Project: Ratis
          Issue Type: Bug
          Components: client
    Affects Versions: 0.6.0
            Reporter: Burcu Ozkan


While running a Netty cluster, RaftClient is blocked after it submits a request to the leader which is partitioned from the cluster.

The attached test reproduces the problem. In the test, after the client connects to the leader, the leader is disconnected and another node is elected as the new leader. However, the client waits indefinitely for a reply from the previous one.

The test passes for Grpc and HadoopRpc, but fails with TestTimedOutException for Netty.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)