hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-457) Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl
Date Mon, 01 Apr 2013 16:55:16 GMT

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

Vinod Kumar Vavilapalli commented on YARN-457:
----------------------------------------------

[~kj-ki], the correct way to fix this is to use {{initLocalNewNodeReportList()}} also in {{setUpdatedNodes()}}.
See how {{getAllocatedContainers()}} and {{setAllocatedContainers()}} are implemented for
example.
                
> Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl
> ----------------------------------------------------------------------------
>
>                 Key: YARN-457
>                 URL: https://issues.apache.org/jira/browse/YARN-457
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sandy Ryza
>            Assignee: Kenji Kikushima
>            Priority: Minor
>              Labels: Newbie
>         Attachments: YARN-457.patch
>
>
> {code}
>     if (updatedNodes == null) {
>       this.updatedNodes.clear();
>       return;
>     }
> {code}
> If updatedNodes is already null, a NullPointerException is thrown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message