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

Posted to issues@flink.apache.org by "Jenas Zhang (Jira)" <ji...@apache.org> on 2019/09/27 10:29:00 UTC

[jira] [Commented] (FLINK-10030) zookeeper jobgraphs job info cannot be removed when the job is cancelled with zk ha mode

    [ https://issues.apache.org/jira/browse/FLINK-10030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939311#comment-16939311 ] 

Jenas Zhang commented on FLINK-10030:
-------------------------------------

+1

I don't know whether we can add one existence check after sending out the zookeeper request even without exception.

> zookeeper jobgraphs job info cannot be removed when the job is cancelled with zk ha mode
> ----------------------------------------------------------------------------------------
>
>                 Key: FLINK-10030
>                 URL: https://issues.apache.org/jira/browse/FLINK-10030
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.5.0, 1.8.1
>            Reporter: qiang.li
>            Priority: Critical
>
> flink 1.5 with zk ha mode,when a job is cancelled,if you restart the cluster,the jobmanager will fail because of missing the blob data. I find that  the information about the job in zk node jobgraphs cannot be removed due to the standby jobmanager lock the node.I think that standby jobmanager should not be watch the jobgraphs node.



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