[
https://issues.apache.org/jira/browse/YARN-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223142#comment-14223142
]
Hadoop QA commented on YARN-2025:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12643596/YARN-2025.1.patch
against trunk revision 555fa2d.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5916//console
This message is automatically generated.
> Possible NPE in schedulers#addApplicationAttempt()
> --------------------------------------------------
>
> Key: YARN-2025
> URL: https://issues.apache.org/jira/browse/YARN-2025
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Tsuyoshi OZAWA
> Assignee: Tsuyoshi OZAWA
> Attachments: YARN-2025.1.patch
>
>
> In FifoScheduler/FairScheduler/CapacityScheduler#addApplicationAttempt(), we
> don't check whether {{application}} is null. This can cause NPE in following
> sequences: addApplication() -> doneApplication() (e.g. AppKilledTransition)
> -> addApplicationAttempt().
> {code}
> SchedulerApplication application =
> applications.get(applicationAttemptId.getApplicationId());
> String user = application.getUser();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
