You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Xiangdong Huang (Jira)" <ji...@apache.org> on 2020/03/24 03:15:00 UTC

[jira] [Assigned] (IOTDB-554) [Distributed] Add the ability to resolve log inconsistencies for AppendEntries request

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

Xiangdong Huang reassigned IOTDB-554:
-------------------------------------

    Assignee: Tan xinyu

> [Distributed] Add the ability to resolve log inconsistencies for AppendEntries request
> --------------------------------------------------------------------------------------
>
>                 Key: IOTDB-554
>                 URL: https://issues.apache.org/jira/browse/IOTDB-554
>             Project: Apache IoTDB
>          Issue Type: Improvement
>          Components: Core/Cluster
>            Reporter: Tan xinyu
>            Assignee: Tan xinyu
>            Priority: Major
>              Labels: distributed
>
> Currently the leader use heartbeat requests to periodically resolve log conflicts, while AppendEntries is only used to synchronize the latest log entry, even if the logs do not match. If there is an inconsistency in the log between nodes, the leader can only wait for a periodic heartbeat to try to solve it, but cannot solve it in a short time, which eventually leads to poor read performance. In fact, the leader should try to resolve the conflict as soon as they encounter a conflict after sending an AppendEntries request.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)