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/11/29 23:37:00 UTC
[jira] [Updated] (RATIS-443) FollowerState.inLogSync can be
incorrectly cleared in appendEntriesAsync
[ https://issues.apache.org/jira/browse/RATIS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo Nicholas Sze updated RATIS-443:
--------------------------------------
Description: FollowerState.inLogSync is to indicate that the follower is writing log/statemachine data. So that it should not time out to start a leader election. However, it is not working correctly in the async case: suppose there are two or more outstanding appendEntriesAsync calls, the first completed call will clear inLogSync even if the other calls are still in progress. (was: FollowerState.inLogSync is to indicate that the follower is write log/statemachine data so that it should not time out to start a leader election. However, it is not working correctly in the async case: suppose there are two or more outstanding appendEntriesAsync calls, the first completed call will clear inLogSync even if the other calls are still in progress.)
> FollowerState.inLogSync can be incorrectly cleared in appendEntriesAsync
> ------------------------------------------------------------------------
>
> Key: RATIS-443
> URL: https://issues.apache.org/jira/browse/RATIS-443
> Project: Ratis
> Issue Type: Bug
> Components: server
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
>
> FollowerState.inLogSync is to indicate that the follower is writing log/statemachine data. So that it should not time out to start a leader election. However, it is not working correctly in the async case: suppose there are two or more outstanding appendEntriesAsync calls, the first completed call will clear inLogSync even if the other calls are still in progress.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)