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

Lokesh Jain commented on RATIS-225:
-----------------------------------

The v1 patch modifies the test for appendEntryTimeout to test the scenario. 
Without the update on heartbeat the modified test fails with 
IllegalStateException. This happens because the follower next index is not 
updated on leader as we have blocked the append entry replies in the test. 
After the retry cache timeout the client request is accepted again by the 
leader which leads to IllegalStateException.

This scenario is avoided if the leader is updated on every heartbeat.

> Grpc LogAppender should update next index on heartbeat reply
> ------------------------------------------------------------
>
>                 Key: RATIS-225
>                 URL: https://issues.apache.org/jira/browse/RATIS-225
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Lokesh Jain
>            Assignee: Lokesh Jain
>            Priority: Major
>         Attachments: RATIS-225.001.patch
>
>
> Grpc LogAppender currently does not update next index in heartbeat reply. In 
> case the previous appendEntry times out the next index may not be updated in 
> the leader for a long time. Therefore we need to update the next index on a 
> heartbeat success.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to