hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4338) NPE in RegularContainerAllocator.preCheckForNewContainer()
Date Tue, 10 Nov 2015 01:40:11 GMT

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

Naganarasimha G R commented on YARN-4338:
-----------------------------------------

IMHO, i think its worth a try as anyway null is treated as default Label so funcationally
its fine. Even if it fails I expect some test cases failing but it will prevent future testcases
not require to handle this explicitly. Thoughts ?


> NPE in RegularContainerAllocator.preCheckForNewContainer()
> ----------------------------------------------------------
>
>                 Key: YARN-4338
>                 URL: https://issues.apache.org/jira/browse/YARN-4338
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Xinwei Qin 
>            Priority: Minor
>         Attachments: YARN-4338.001.patch
>
>
> The codes in RegularContainerAllocator.preCheckForNewContainer():
> {code}
>     if (anyRequest.getNodeLabelExpression()
>         .equals(RMNodeLabelsManager.NO_LABEL)) {
>       missedNonPartitionedRequestSchedulingOpportunity =
>           application
>               .addMissedNonPartitionedRequestSchedulingOpportunity(priority);
>     }
> {code}
> {code}anyRequest.getNodeLabelExpression(){code}may return null.



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

Mime
View raw message