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

Posted to issues@ratis.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2018/01/03 14:27:00 UTC

[jira] [Commented] (RATIS-177) Raft Leader should not return LeaderNotReady Exception for old completed requests

    [ https://issues.apache.org/jira/browse/RATIS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309709#comment-16309709 ] 

Tsz Wo Nicholas Sze commented on RATIS-177:
-------------------------------------------

[~ljain], in the patch, if cacheEntry != null, does it imply that leaderState.isReady() == true?

How could a leader return LeaderNotReady Exception for old completed requests?  Could you suggest a test?

> Raft Leader should not return LeaderNotReady Exception for old completed requests
> ---------------------------------------------------------------------------------
>
>                 Key: RATIS-177
>                 URL: https://issues.apache.org/jira/browse/RATIS-177
>             Project: Ratis
>          Issue Type: Bug
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>         Attachments: RATIS-177.001.patch
>
>
> Currently Raft Leader returns LeaderNotReady Exception for all the requests coming to the server. We should return the reply in case the request has already been completed normally.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)