[
https://issues.apache.org/jira/browse/YARN-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174480#comment-14174480
]
Wangda Tan commented on YARN-2699:
----------------------------------
The exception is,
{code}
2014-10-16 16:41:11,681 FATAL resourcemanager.ResourceManager
(ResourceManager.java:run(668)) - Error in handling event type NODE_ADDED to
the scheduler
java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.resourcemanager.nodelabels.RMNodeLabelsManager.activateNode(RMNodeLabelsManager.java:186)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addNode(CapacityScheduler.java:1124)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:1035)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:1)
at
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:659)
at java.lang.Thread.run(Thread.java:744)
{code}
And attached a new fix handle the case that some test cases may unintentionally
specified a nodeId with port = 0, we shouldn't raise any exception in
NodeLabelManager side.
> Fix test timeout in TestResourceTrackerOnHA#testResourceTrackerOnHA
> -------------------------------------------------------------------
>
> Key: YARN-2699
> URL: https://issues.apache.org/jira/browse/YARN-2699
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: client
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
> Attachments: YARN-2699-20141016-1.patch
>
>
> Because of changes by YARN-2500/YARN-2496/YARN-2494, now registering a node
> manager with port=0 is not allowed.
> TestResourceTrackerOnHA#testResourceTrackerOnHA will be failed since it
> register a node manager with port = 0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
