[
https://issues.apache.org/jira/browse/YARN-6598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010742#comment-16010742
]
Hudson commented on YARN-6598:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11734 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11734/])
YARN-6598. History server getApplicationReport NPE when fetching report
(jeagles: rev c48f2976a3de60b95c4a5ada4f0131c4cdde177a)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/TestApplicationHistoryManagerOnTimelineStore.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/ApplicationHistoryManagerOnTimelineStore.java
> History server getApplicationReport NPE when fetching report for pre-2.8 job
> ----------------------------------------------------------------------------
>
> Key: YARN-6598
> URL: https://issues.apache.org/jira/browse/YARN-6598
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Affects Versions: 2.8.0
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Blocker
> Attachments: YARN-6598.001.patch
>
>
> ApplicationHistoryManagerOnTimelineStore#convertToApplicationReport can NPE
> for a job that was run prior to the cluster upgrading to 2.8. It blindly
> assumes preemption metrics are present when CPU metrics are present, and when
> they are not it triggers the NPE.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
