You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Ricky Burnett (Jira)" <ji...@apache.org> on 2021/03/25 21:29:00 UTC
[jira] [Created] (FLINK-21980) ZooKeeperRunningJobsRegistry creates
an empty znode
Ricky Burnett created FLINK-21980:
-------------------------------------
Summary: ZooKeeperRunningJobsRegistry creates an empty znode
Key: FLINK-21980
URL: https://issues.apache.org/jira/browse/FLINK-21980
Project: Flink
Issue Type: Bug
Components: Client / Job Submission
Affects Versions: 1.12.2
Reporter: Ricky Burnett
ZooKeeperRunningJobsRegistry#writeEnumToZooKeeper calls
{code:java}
this.client.newNamespaceAwareEnsurePath(zkPath).ensure(client.getZookeeperClient());{code}
This creates an empty znode in zookeeper. If the job manager is interrupted at this point the job manager cannot recover. When trying to restore jobs on a restarted job manager, ZooKeeperRunningJobsRegistry#getJobSchedulingStatus will throw an exception due to the empty znode.
Behavior was verified in a test environment where the job manager was interrupted at that point in execution leaving ZK in the following state:
{code:java}
zk: localhost:2181(CONNECTED) 2] ls /flink/default
[checkpoint-counter, checkpoints, jobgraphs, leader, leaderlatch, running_job_registry]
[zk: localhost:2181(CONNECTED) 3] ls /flink/default/running_job_registry
[c982053dd0b9100967e6a9d89202f2a5]
[zk: localhost:2181(CONNECTED) 4] get /flink/default/running_job_registry/c982053dd0b9100967e6a9d89202f2a5
[zk: localhost:2181(CONNECTED) 5]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)