[
https://issues.apache.org/jira/browse/ZOOKEEPER-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949116#comment-17949116
]
Li Wang edited comment on ZOOKEEPER-4927 at 5/3/25 1:48 AM:
------------------------------------------------------------
{code:java}
autopurge.purgeInterval : (No Java system property) New in 3.4.0: The time
interval in hours for which the purge task has to be triggered. Set to a
positive integer (1 and above) to enable the auto purging. Defaults to 0.
{code}
was (Author: liwang):
{quote}autopurge.purgeInterval : (No Java system property) New in 3.4.0: The
time interval in hours for which the purge task has to be triggered. Set to a
positive integer (1 and above) to enable the auto purging. Defaults to 0.{quote}
> Support more fine tunable purgeInterval
> ---------------------------------------
>
> Key: ZOOKEEPER-4927
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4927
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.9.3
> Reporter: Li Wang
> Priority: Major
>
> A zookeeper instance went down in prod because it ran out of disk space. It
> turned out that the purge task was not able to keep up with the rate of
> snapshot taken. A new snapshot was taken after 1 min.
> Too snapshots were generate during autoPurge.purgeInterval. Since the unit is
> hour, so the min internal is 1 hour.
> To support writes heavy use case, we would need to support more fine tuned
> purge interval. For example, in minutes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
