[
https://issues.apache.org/jira/browse/FLINK-20695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-20695.
---------------------------------
Fix Version/s: 1.12.4
1.13.1
Resolution: Fixed
Fixed via
1.14.0: 8cf6f84f1b99ae19ddd18e38a370d5f47325b6f1
1.13.1: 57bc204c5757b47a30dddd6c12029416b94e1331
1.12.4: 814fc656e21dedcb99827c76c078217a57d94bc5
> 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
> Fix For: 1.14.0, 1.13.1, 1.12.4
>
>
> 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)
