[
https://issues.apache.org/jira/browse/FLINK-20695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325363#comment-17325363
]
Flink Jira Bot commented on FLINK-20695:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Zookeeper node under leader and leaderlatch is not deleted after job finished
> -----------------------------------------------------------------------------
>
> Key: FLINK-20695
> URL: https://issues.apache.org/jira/browse/FLINK-20695
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.9.0, 1.11.3, 1.12.0, 1.13.0
> Reporter: lidesheng
> Assignee: Yi Tang
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.13.0
>
>
> I used flink 1.11 in standalone cluster mode for batch job. The enviornment
> was configured as zookeeper HA mode.
> After job was commited, flink runtime created nodes under
> /flink/default/leader and /flink/default/leaderlatch with job id. Though
> jobs were finished, these nodes were remaining in zookeeper path forever.
> After a period of running, more and more jobs had been executed and there
> were a greate number of nodes under /flink/default/leader and slowed down the
> performance of zookeeper. Why not delete the nodes after job finished? Flink
> runtime could get job status by listeners and delete the leader nodes for job
> immidiately.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
