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

Posted to issues@ratis.apache.org by "Lokesh Jain (Jira)" <ji...@apache.org> on 2020/04/27 11:24:00 UTC

[jira] [Updated] (RATIS-844) Support timeout for client blocking api (Netty)

     [ https://issues.apache.org/jira/browse/RATIS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lokesh Jain updated RATIS-844:
------------------------------
    Summary: Support timeout for client blocking api (Netty)  (was: RaftClient should connect to the new leader when the old leader is partitioned from the cluster)

> Support timeout for client blocking api (Netty)
> -----------------------------------------------
>
>                 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
>            Priority: Major
>         Attachments: RATIS-844.001.patch, RATIS-844.002.patch, RATIS-844.003.patch
>
>
> 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)