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/07/20 21:27:00 UTC

[jira] [Updated] (RATIS-139) RaftLogWorker should use two task queues.

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

Tsz Wo Nicholas Sze updated RATIS-139:
--------------------------------------
    Component/s: server

> RaftLogWorker should use two task queues. 
> ------------------------------------------
>
>                 Key: RATIS-139
>                 URL: https://issues.apache.org/jira/browse/RATIS-139
>             Project: Ratis
>          Issue Type: Improvement
>          Components: server
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jing Zhao
>            Priority: Major
>
> {code}
>   private boolean shouldFlush() {
>     return pendingFlushNum >= forceSyncNum ||
>         (pendingFlushNum > 0 && queue.isEmpty());
>   }
> {code}
> It is possible that queue is often non-empty, but not full to trigger force sync. We could use two queues similar to two buffer approach in HDFS edit logs.



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