You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Andrey Yegorov (JIRA)" <ji...@apache.org> on 2016/11/11 08:14:59 UTC

[jira] [Updated] (BOOKKEEPER-968) Entry log flushes happen on log rotation and cause long spikes in IO utilization

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

Andrey Yegorov updated BOOKKEEPER-968:
--------------------------------------
    Description: 
Caught this issue on the servers with 128G of RAM. This is probably not an issue on servers/VMs with less RAM.

With current implementation we end up with single entry log flush during log rotation.
OS tries to flush everything as fast as possible and saturates disk. This results in long periods of high latency (reads and writes).
 

  was:
Caught this issue on the servers with 128G of RAm. This is probably not an issue on servers/VMs with less RAM.

With current implementation we end up with single entry log flush during log rotation.
OS tries to flush everything as fast as possible and saturates disk. This results in long periods of high latency (reads and writes).
 


> Entry log flushes happen on log rotation and cause long spikes in IO utilization
> --------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-968
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-968
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>    Affects Versions: 4.5.0
>            Reporter: Andrey Yegorov
>            Assignee: Andrey Yegorov
>            Priority: Minor
>
> Caught this issue on the servers with 128G of RAM. This is probably not an issue on servers/VMs with less RAM.
> With current implementation we end up with single entry log flush during log rotation.
> OS tries to flush everything as fast as possible and saturates disk. This results in long periods of high latency (reads and writes).
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)