[
https://issues.apache.org/jira/browse/ZOOKEEPER-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839761#comment-16839761
]
Hudson commented on ZOOKEEPER-3244:
-----------------------------------
SUCCESS: Integrated in Jenkins build Zookeeper-trunk-single-thread #355 (See
[https://builds.apache.org/job/Zookeeper-trunk-single-thread/355/])
ZOOKEEPER-3244: Add option to snapshot based on log size (andor: rev
31e92e0a4f287ca840e0c9418e3a9b706e9721db)
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/persistence/FileTxnSnapLog.java
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/persistence/FileTxnLog.java
* (edit)
zookeeper-server/src/test/java/org/apache/zookeeper/test/RestoreCommittedLogTest.java
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/SyncRequestProcessor.java
* (edit) zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/ZKDatabase.java
* (edit)
zookeeper-server/src/main/java/org/apache/zookeeper/server/persistence/TxnLog.java
> Add option to snapshot based on log size
> ----------------------------------------
>
> Key: ZOOKEEPER-3244
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3244
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Reporter: Brian Nixon
> Assignee: Brian Nixon
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.6.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Currently, ZooKeeper only takes snapshot based on the snap count. If the
> workload on an ensemble includes large txns then we'll end up with large
> amount data kept on disk, and might have a low disk space issue.
> Add a maximum limit on the total size of the log files between each snapshot.
> This will change the snap frequency, which means with the same snap retention
> number a server will eat up less disk.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)