[
https://issues.apache.org/jira/browse/YARN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340718#comment-14340718
]
Vinod Kumar Vavilapalli commented on YARN-964:
----------------------------------------------
Old JIRA. The right solution is not an AM-retry interval but launching the AM
somewhere. Although, the situation should be better with YARN-1781 / YARN-257 -
can you use the configuration
(yarn.nodemanager.disk-health-checker.max-disk-utilization-per-disk-percentage)
added at YARN-1781?
> Give a parameter that can set AM retry interval
> ------------------------------------------------
>
> Key: YARN-964
> URL: https://issues.apache.org/jira/browse/YARN-964
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Affects Versions: 2.3.0
> Reporter: qus-jiawei
>
> Our am retry number is 4.
> As one nodemanager 's disk is full,the container of am couldn't allocate on
> this nodemanager.But RM try this AM on the same NM every 3 secondes.
> i think there shoule be a params to set the AM retry interval.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
