Flink 1.7.2: Continuously getting job not found exception

[HarshithBolar]

Hi all,

 

We’ve recently upgraded our Flink cluster from 1.4.2 to 1.7.2. Everything was fine until today when I started getting the following exceptions in the job manager logs.

 

There was a job running on the cluster but it was cancelled. But it looks like the REST handler is looking for that job for some reason and failing. Any advice on how to troubleshoot and stop this?

 

Thanks,

Harshith

[Oytun Tez]

You may have forgotten the Web UI open somewhere, before the new job deployment, which keeps trying to get updates on that previous job.

On Tue, Apr 16, 2019 at 11:09 AM Kumar Bolar, Harshith <[hidden email]> wrote:

Hi all,

 

We’ve recently upgraded our Flink cluster from 1.4.2 to 1.7.2. Everything was fine until today when I started getting the following exceptions in the job manager logs.

 

There was a job running on the cluster but it was cancelled. But it looks like the REST handler is looking for that job for some reason and failing. Any advice on how to troubleshoot and stop this?

 

Thanks,

Harshith

[HarshithBolar]

That was it. The errors stopped after closing the forgotten web dashboard.

 

Regards,

Harshith

 

From: Oytun Tez <[hidden email]>
Date: Tuesday, 16 April 2019 at 8:41 PM
To: Harshith Kumar Bolar <[hidden email]>
Cc: user <[hidden email]>
Subject: [External] Re: Flink 1.7.2: Continuously getting job not found exception

 

You may have forgotten the Web UI open somewhere, before the new job deployment, which keeps trying to get updates on that previous job.

 

---

Oytun Tez

 

M O T A W O R D

The World's Fastest Human Translation Platform.

[hidden email] — www.motaword.com

 

 

On Tue, Apr 16, 2019 at 11:09 AM Kumar Bolar, Harshith <[hidden email]> wrote:

Hi all,

 

We’ve recently upgraded our Flink cluster from 1.4.2 to 1.7.2. Everything was fine until today when I started getting the following exceptions in the job manager logs.

 

There was a job running on the cluster but it was cancelled. But it looks like the REST handler is looking for that job for some reason and failing. Any advice on how to troubleshoot and stop this?

 

Thanks,

Harshith