[
https://issues.apache.org/jira/browse/ZOOKEEPER-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Li Wang updated ZOOKEEPER-4927:
-------------------------------
Description:
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.
was:
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.
> 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)
