hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1444) RM crashes when node resource request sent without corresponding rack request
Date Mon, 25 Nov 2013 23:24:35 GMT

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

Bikas Saha commented on YARN-1444:

Marking this as blocker since this makes it easy to crash and DOS the RM by specifying incorrect
input. This can be disastrous in real life when a buggy app can bring the entire cluster down.
We should definitely fix this. If other committers think differently then please downgrade
the priority.

> RM crashes when node resource request sent without corresponding rack request
> -----------------------------------------------------------------------------
>                 Key: YARN-1444
>                 URL: https://issues.apache.org/jira/browse/YARN-1444
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client, resourcemanager
>            Reporter: Robert Grandl
>            Priority: Blocker
>             Fix For: 2.3.0
> I have tried to force reducers to execute on certain nodes. What I did is I changed for
reduce tasks, the RMContainerRequestor#addResourceRequest(req.priority, ResourceRequest.ANY,
req.capability) to RMContainerRequestor#addResourceRequest(req.priority, HOST_NAME, req.capability).

> However, this change lead to RM crashes when reducers needs to be assigned with the following
> FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in handling
event type NODE_UPDATE to the scheduler
> java.lang.NullPointerException
>     at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.assignContainers(LeafQueue.java:841)
>     at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.assignContainersToChildQueues(ParentQueue.java:640)
>     at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.assignContainers(ParentQueue.java:554)
>     at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.nodeUpdate(CapacityScheduler.java:695)
>     at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:739)
>     at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:86)
>     at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:549)
>     at java.lang.Thread.run(Thread.java:722)

This message was sent by Atlassian JIRA

View raw message