[
https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naganarasimha G R updated YARN-3554:
------------------------------------
Attachment: YARN-3554.20150429-1.patch
Hi [~jlowe], as it was simple fix i have assigned to my self, hope you were not
already working on it
I think earlier intention was to sync with
{{yarn.resourcemanager.connect.max-wait.ms}} which is also 900000. but i feel
it should be 10 mins as per the description given by you. Attaching the patch
for the same
> 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
> Attachments: 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)
