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/10 02:26:00 UTC

[jira] [Commented] (RATIS-406) In RaftServerImpl, the RaftLog.append(entries) call should not hold the RaftServerImpl lock

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

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

r406_20181109.patch: 1st patch.

> In RaftServerImpl, the RaftLog.append(entries) call should not hold the RaftServerImpl lock
> -------------------------------------------------------------------------------------------
>
>                 Key: RATIS-406
>                 URL: https://issues.apache.org/jira/browse/RATIS-406
>             Project: Ratis
>          Issue Type: Improvement
>          Components: server
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Major
>         Attachments: r406_20181109.patch
>
>
> In RaftServerImpl, the appendEntriesAsync(..) calls must be sequential (although the actual log I/O is async).  Otherwise, the entries appended may be out of order.
> As a result, RaftLog.append(entries) needs not to hold the RaftServerImpl lock.



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