Re: Exception: Coordinator of operator xxxx does not exist or the job vertex this operator belongs to is not initialized.

Hi Biao, I agree with you that this exception is not very meaningful and can be noisy in the JM logs, especially when running large-scale batch jobs in a session cluster. IIRC, there isn't a current config to filter out or silence such exceptions in batch mode. So I've created a JIRA ticket (

Re: Exception: Coordinator of operator xxxx does not exist or the job vertex this operator belongs to is not initialized.

Hi Junrui, Thanks for your answer! Since this exception is not very meaningful, is there a solution or a flink config to filter out or silent such exception in batch mode? When I run some large scale batch jobs in a session cluster, it turns out that the JM log will be fulfilled with this

Re: Exception: Coordinator of operator xxxx does not exist or the job vertex this operator belongs to is not initialized.

Hi, This exception is common in batch jobs and is caused by the collect sink attempting to fetch data from the corresponding operator coordinator on the JM based on the operator ID. However, due to the sequential scheduling of batch jobs, if a job vertex has not been initialized yet, the

Exception: Coordinator of operator xxxx does not exist or the job vertex this operator belongs to is not initialized.

When I run a batch job using Flink 1.19, I used collect() in the job, and many times the following error appears in the JobManager log: Caused by: org.apache.flink.util.FlinkException: Coordinator of operator does not exist or the job vertex this operator belongs to is not initialized.