[
https://issues.apache.org/jira/browse/MAPREDUCE-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210653#comment-13210653
]
Hadoop QA commented on MAPREDUCE-3730:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12515032/MAPREDUCE-3730.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 12 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1889//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1889//console
This message is automatically generated.
> Allow restarted NM to rejoin cluster before RM expires it
> ---------------------------------------------------------
>
> Key: MAPREDUCE-3730
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3730
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv2, resourcemanager
> Affects Versions: 0.23.1, 0.24.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Minor
> Fix For: 0.23.2
>
> Attachments: MAPREDUCE-3730.patch, MAPREDUCE-3730.patch,
> MAPREDUCE-3730.patch
>
>
> When a node in the RUNNING state (healthy or unhealthy) is rebooted, the
> resourcemanager rejects the nodemanager's registration request as a duplicate
> because it is convinced that the nodemanager is already running on that node.
> It won't allow that node to rejoin the cluster until the node expiration
> time elapses which is 10min+ by default. We should allow the NM to rejoin
> the cluster if it re-registers within the expiration timeout.
> Note that this problem occurs with NMs that are configured to specific ports.
> If ephemeral ports are used then a NM reboot "works" because the RM thinks
> the NM registration is for a new node. See the discussions in MAPREDUCE-3070
> and MAPREDUCE-3363.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
