Vinod Kumar Vavilapalli commented on YARN-3554:

bq. 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.
For our users, we explicitly set yarn.client.nodemanager-connect.max-wait-ms to 
60,000 (one minute). As HADOOP-11398 is still not in, this ends up becoming 6 
minutes timeout (assuming each of the underlying rpc retries takes 1 sec * 50 
times to finish (50 secs), plus 10 seconds retry interval, causing 1min per 
retry and 6 retries overall).

> 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

Reply via email to