hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high
Date Wed, 06 May 2015 19:17:01 GMT

    [ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531224#comment-14531224

Naganarasimha G R commented on YARN-3554:

if there are plans to get HADOOP-11398 faster then we can directly modify  yarn.client.nodemanager-connect.max-wait-ms
to 3mins, if not i feel it would be better to modify it to 1min and drop a comment in HADOOP-11398
to remodify this value back to 3 once its in . thoughts?

> 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: BB2015-05-TBR, 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

View raw message