[
https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525245#comment-14525245
]
Naganarasimha G R commented on YARN-3554:
-----------------------------------------
Hi [~gtCarrera9],
Thanks for commenting on this jira but did not get the intention completely,
whether you are expecting me to merge the changes required for 3518 here ?
if so i had few questions
1. yarn-3518 tries to modify default value of
yarn.resourcemanager.connect.max-wait.ms from 900000 to 600000, which not only
impacts timeout from AM - RM but also NM - RM and client(cli, web, application
report etc..) - RM. Is that ok ? (I am ok with it but just wanted to point it
out)
2. Given the current high availability, is it required to wait for 10 mins to
detect that RM has failed is valid or shall i decrease that too to 3 mins ?
If you inform i can merge the changes of 3518 and also update in
yarn-default.xml which is missing in 3518.
> Default value for maximum nodemanager connect wait time is too high
> -------------------------------------------------------------------
>
> Key: YARN-3554
> URL: https://issues.apache.org/jira/browse/YARN-3554
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
> Assignee: Naganarasimha G R
> Labels: newbie
> Attachments: YARN-3554-20150429-2.patch, YARN-3554.20150429-1.patch
>
>
> The default value for yarn.client.nodemanager-connect.max-wait-ms is 900000
> msec or 15 minutes, which is way too high. The default container expiry time
> from the RM and the default task timeout in MapReduce are both only 10
> minutes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
