[
https://issues.apache.org/jira/browse/FLINK-33053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762962#comment-17762962
]
Matthias Pohl commented on FLINK-33053:
---------------------------------------
Thanks for sharing this. I guess, the thread dump (which you can generate by
sending {{kill -3 <pid>}} to the TaskManager process) would be more helpful
than the heap dump. Or am I missing something. The thread dump might tell us
more of what threads are still available even after the JobMaster is closed.
> Watcher leak in Zookeeper HA mode
> ---------------------------------
>
> Key: FLINK-33053
> URL: https://issues.apache.org/jira/browse/FLINK-33053
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.17.0, 1.17.1
> Reporter: Yangze Guo
> Priority: Critical
> Attachments: 26.dump.zip, 26.log
>
>
> We observe a watcher leak in our OLAP stress test when enabling Zookeeper HA
> mode. TM's watches on the leader of JobMaster has not been stopped after job
> finished.
> Here is how we re-produce this issue:
> - Start a session cluster and enable Zookeeper HA mode.
> - Continuously and concurrently submit short queries, e.g. WordCount to the
> cluster.
> - echo -n wchp | nc \{zk host} \{zk port} to get current watches.
> We can see a lot of watches on
> /flink/\{cluster_name}/leader/\{job_id}/connection_info.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
