You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/05/14 09:16:00 UTC
[jira] [Resolved] (FLINK-12472) Support setting
attemptFailuresValidityInterval of jobs on Yarn
[ https://issues.apache.org/jira/browse/FLINK-12472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-12472.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed via 6231b18645dd41031299b7071d20ddea32c60457
> Support setting attemptFailuresValidityInterval of jobs on Yarn
> ---------------------------------------------------------------
>
> Key: FLINK-12472
> URL: https://issues.apache.org/jira/browse/FLINK-12472
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: Victor Wong
> Assignee: Victor Wong
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> According to the documentation of [Yarn|http://hadoop.apache.org/docs/r2.6.0/api/org/apache/hadoop/yarn/api/records/ApplicationSubmissionContext.html], a yarn application can set a _attemptFailuresValidityInterval_ to reset application attempts.
>
> "attemptFailuresValidityInterval. _The default value is -1. when attemptFailuresValidityInterval in milliseconds is set to > 0, the failure number will no take failures which happen out of the validityInterval into failure count. If failure count reaches to maxAppAttempts, the application will be failed."_
>
> We can make use of this feature to make Flink jobs on Yarn to be more long-running.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)