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

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

This can happen during normal operation as well. Suppose the 
appendEntryRequest1 was sent. It has some 100 entries whose state machine data 
needs to be written. Now the reply for this request would be sent after all 100 
entries have been written to the state machine.

Now if another appendEntryRequest2 is sent with just one entry. This request 
might receive a reply earlier as its stateMachineData is less comparatively. 
This would happen after I changed pendingRequests from queue to a map in 
RATIS-217.

Yes, we should update match index in strict order.

> 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