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

Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/31 23:25:02 UTC

[jira] [Closed] (FLINK-17871) Make the default value of attemptFailuresValidityInterval more reasonable

     [ https://issues.apache.org/jira/browse/FLINK-17871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot closed FLINK-17871.
----------------------------------
    Resolution: Auto Closed

This issue was labeled "stale-minor" 7 ago and has not received any updates so I have gone ahead and closed it.  If you are still affected by this or would like to raise the priority of this ticket please re-open, removing the label "auto-closed" and raise the ticket priority accordingly.


> Make the default value of attemptFailuresValidityInterval more reasonable
> -------------------------------------------------------------------------
>
>                 Key: FLINK-17871
>                 URL: https://issues.apache.org/jira/browse/FLINK-17871
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>            Reporter: fanxin
>            Priority: Minor
>              Labels: auto-closed
>
> Default value of `yarn.application-attempt-failures-validity-interval` is `10000` milliseconds at present. Usually preparing the context alone can take seconds, which means that default value of 10000 is too small to even prepare the runtime context. With a default config, a flink on yarn job in will hardly meet the condition of ”fail 2 times in 10s“. If the job has some internal problems, unfortunately, it can easily get bogged down in endless retries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)