[
https://issues.apache.org/jira/browse/FLINK-22506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337510#comment-17337510
]
Till Rohrmann commented on FLINK-22506:
---------------------------------------
Ok, then I have misunderstood the ticket a bit. I thought that any application
master failure would be handled as a failed attempt and counts towards the
{{yarn.application-attempts}}. I don't think that we ever mark an Yarn attempt
explicitly as failed. Hence, I thought that it should work with
{{yarn.application-attempts}} and
{{yarn.application-attempt-failures-validity-interval}}.
> YARN job cluster stuck in retrying creating JobManager if savepoint is
> corrupted
> --------------------------------------------------------------------------------
>
> Key: FLINK-22506
> URL: https://issues.apache.org/jira/browse/FLINK-22506
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.11.3
> Reporter: Paul Lin
> Priority: Major
> Attachments: corrupted_savepoint.log, yarn application attempts.png
>
>
> If a non-retryable error (e.g. the savepoint is corrupted or unaccessible)
> occurs during the initiation of the job manager, the job cluster exits with
> an error code. But since it does not mark the attempt as failed, it won't be
> count as a failed attempt, and YARN will keep retrying forever.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
