Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 25 Apr 2015 14:41:38 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12822611.1429607436000.27791.1429972898826@Atlassian.JIRA>
In-Reply-To: <JIRA.12822611.1429607436000@Atlassian.JIRA>
References: <JIRA.12822611.1429607436000@Atlassian.JIRA>
 <JIRA.12822611.1429607436525@arcas>
Subject: [jira] [Commented] (YARN-3518) default rm/am expire interval should
 not less than default resourcemanager connect wait time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hadoop QA commented on YARN-3518:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 36s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace. |
| {color:green}+1{color} | javac |   7m 30s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 32s | There were no new javadoc warning messages. |
| {color:green}+1{color} | release audit |   0m 22s | The applied patch does not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   5m 19s | There were no new checkstyle issues. |
| {color:green}+1{color} | install |   1m 33s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 33s | The patch built with eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   1m 23s | The patch does not introduce any new Findbugs (version 2.0.3) warnings. |
| {color:green}+1{color} | yarn tests |   0m 26s | Tests passed in hadoop-yarn-api. |
| | |  41m 17s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12728151/YARN-3518.001.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 78c6b46 |
| hadoop-yarn-api test log | https://builds.apache.org/job/PreCommit-YARN-Build/7501/artifact/patchprocess/testrun_hadoop-yarn-api.txt |
| Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7501/testReport/ |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7501/console |


This message was automatically generated.

> default rm/am expire interval should not less than default resourcemanager connect wait time
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-3518
>                 URL: https://issues.apache.org/jira/browse/YARN-3518
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager, resourcemanager
>            Reporter: sandflee
>         Attachments: YARN-3518.001.patch
>
>
> take am for example, if am can't connect to RM, after am expire (600s), RM relaunch am, and there will be two am at the same time util resourcemanager connect max wait time(900s) passed.
> DEFAULT_RESOURCEMANAGER_CONNECT_MAX_WAIT_MS =  15 * 60 * 1000;
> DEFAULT_RM_AM_EXPIRY_INTERVAL_MS = 600000;
> DEFAULT_RM_NM_EXPIRY_INTERVAL_MS = 600000;


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)