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

Posted to user@flink.apache.org by Hao Sun <ha...@zendesk.com> on 2018/06/05 19:57:47 UTC

Can I control how many times JM trying to rescue a job?

I see a lot of errors because of a job is not found. Can I control this by
config?
Thanks

[image: image.png]

Re: Can I control how many times JM trying to rescue a job?

Posted by Hao Sun <ha...@zendesk.com>.

Thanks!

On Tue, Jun 5, 2018 at 11:49 PM Chesnay Schepler <ch...@apache.org> wrote:

> This is for the REST API, and is often caused by the the UI still being
> open while the cluster was restarted.
> The UI attempts to load the details for the now outdated jobs.
>
> Simply reloading the UI resolves this issue most of the time.
>
>
> On 05.06.2018 21:57, Hao Sun wrote:
>
> I see a lot of errors because of a job is not found. Can I control this by
> config?
> Thanks
>
> [image: image.png]
>
>
>

Re: Can I control how many times JM trying to rescue a job?

Posted by Chesnay Schepler <ch...@apache.org>.

This is for the REST API, and is often caused by the the UI still being 
open while the cluster was restarted.
The UI attempts to load the details for the now outdated jobs.

Simply reloading the UI resolves this issue most of the time.

On 05.06.2018 21:57, Hao Sun wrote:
> I see a lot of errors because of a job is not found. Can I control 
> this by config?
> Thanks
>
> image.png