[
https://issues.apache.org/jira/browse/BOOKKEEPER-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891014#comment-13891014
]
Sijie Guo commented on BOOKKEEPER-717:
--------------------------------------
the first clause is the first time that we find an already timeout entry in the
queue. at this point, we set groupWhenTimeout to true. then it would start
looking forward to see if there any other items in the queue
- if there is no items in the queue, flush current batch.
- if there are still items, then add them into the batch until 1) we find a non
time out entry (the second clause) or 2) we reached the batch size.
> journal should look forward to group time-out entries
> -----------------------------------------------------
>
> Key: BOOKKEEPER-717
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-717
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-717.diff
>
>
> journal should look a bit forward to group timeout entries, which avoid too
> much fsyncs with single entry impacting journal performance. so bookie could
> have sustained high throughput with low-latency.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
