zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3311) Allow a delay to the transaction log flush
Date Wed, 22 May 2019 17:17:00 GMT

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

Hudson commented on ZOOKEEPER-3311:
-----------------------------------

FAILURE: Integrated in Jenkins build Zookeeper-trunk-single-thread #368 (See [https://builds.apache.org/job/Zookeeper-trunk-single-thread/368/])
ZOOKEEPER-3311: Allow a delay to the transaction log flush (eolivelli: rev cc431f70020b9a2028edcc61e41cff9ee85b078f)
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/SyncRequestProcessor.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServerBean.java
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServerMXBean.java


> Allow a delay to the transaction log flush 
> -------------------------------------------
>
>                 Key: ZOOKEEPER-3311
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3311
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Brian Nixon
>            Assignee: Brian Nixon
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The SyncRequestProcessor flushes writes to disk either when 1000 writes are pending to
be flushed or when the processor fails to retrieve another write from its incoming queue.
The "flush when queue empty" condition operates poorly under many workloads as it can quickly
degrade into flushing after every write -- losing all benefits of batching and leading to
a continuous stream of flushes + fsyncs which overwhelm the underlying disk.
>  
> A configurable flush delay would ensure flushes do not happen more frequently than once
every X milliseconds. This can be used in-place of or jointly with batch size triggered flushes.



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

Mime
View raw message