You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/10/14 06:32:00 UTC

[jira] [Updated] (FLINK-19532) FlinkZooKeeperQuorumPeer ignores purge settings

     [ https://issues.apache.org/jira/browse/FLINK-19532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler updated FLINK-19532:
-------------------------------------
    Component/s: Runtime / Coordination

> FlinkZooKeeperQuorumPeer ignores purge settings
> -----------------------------------------------
>
>                 Key: FLINK-19532
>                 URL: https://issues.apache.org/jira/browse/FLINK-19532
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>            Reporter: M L
>            Priority: Minor
>
> After noticing the snapshot/log buildup in our ZooKeeper {{dataDir}}, we tried enabling the purge settings ({{autopurge.snapRetainCount}} and autopurge.purgeInterval).
> Flink's {{FlinkZooKeeperQuorumPeer}} ignores the portion of {{QuorumPeerMain}} which uses those settings and starts up the {{DatadirCleanupManager}}, using only the {{runFromConfig}} method.
> Is this intentional and is the recommended way to handle snapshot buildup with the built in ZooKeeper to use the {{PurgeTxnLog}} utility?
> It would make sense to enable to support the {{DatadirCleanupManager}} as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)