You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2013/04/01 18:47:16 UTC

[jira] [Assigned] (YARN-457) Setting updated nodes from null to null causes NPE in AMResponsePBImpl

     [ https://issues.apache.org/jira/browse/YARN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli reassigned YARN-457:
--------------------------------------------

    Assignee: Kenji Kikushima

Kenji, assigning this to you. In future, it will be great if you
 - put a comment that you are working on it
 - put a summary of what the patch does.
Thanks.
                
> Setting updated nodes from null to null causes NPE in AMResponsePBImpl
> ----------------------------------------------------------------------
>
>                 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