hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high
Date Mon, 04 May 2015 18:21:07 GMT

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

Jason Lowe commented on YARN-3554:

Ah, thanks [~Naganarasimha], sorry I missed that.  We can continue discussing the proper RM
connect wait time over at YARN-3518, as obviously I cannot keep them straight here. ;-)

Are there still objections to lowering it from 15 mins to 3 mins?  I'm +1 for the second patch,
but I'll wait a few days before committing to give time for alternate proposals.

> 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

View raw message