You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2017/11/08 23:29:00 UTC

[jira] [Assigned] (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 ]

Jing Zhao reassigned RATIS-139:
-------------------------------

    Assignee: Jing Zhao

> RaftLogWorker should use two task queues. 
> ------------------------------------------
>
>                 Key: RATIS-139
>                 URL: https://issues.apache.org/jira/browse/RATIS-139
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jing Zhao
>
> {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
(v6.4.14#64029)