[
https://issues.apache.org/jira/browse/ZOOKEEPER-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950173#comment-17950173
]
Li Wang edited comment on ZOOKEEPER-4927 at 5/8/25 3:56 AM:
------------------------------------------------------------
{quote}we may have to fix that before backport.{quote}
How about we keep the original getPurgeInterval() API but add documentation to
indicate it's in milliseconds?
I can submit a fix for the backward compatibility issue.
WDYT?
was (Author: liwang):
{quote}we may have to fix that before backport.{quote}
How about we change
{code:java}
getPurgeIntervalInMs()
{code}
back to
{code:java}
getPurgeInterval()
{code}
. We add it's in milliseconds.
> 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 every a couple of mins.
> 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)
