[
https://issues.apache.org/jira/browse/FLINK-12472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-12472.
-----------------------------------
Resolution: Fixed
Release Note: Yarn's attempt failure validity interval no longer defaults
to the ask timeout `akka.ask.timeout`. Instead it can now be configured
independently via `yarn.application-attempt-failures-validity-interval` whose
default value is `10000` milliseconds.
> 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: 20m
> 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)
