[
https://issues.apache.org/jira/browse/MAPREDUCE-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429789#comment-15429789
]
Hudson commented on MAPREDUCE-6762:
-----------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10316 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10316/])
MAPREDUCE-6762. ControlledJob#toString failed with NPE when job status
(varunsaxena: rev d37b45d613b768950d1cbe342961cd71776816ae)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/Job.java
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/TestJob.java
> ControlledJob#toString failed with NPE when job status is not successfully
> updated
> ----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-6762
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6762
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.7.2
> Reporter: Weiwei Yang
> Fix For: 2.9.0
>
> Attachments: MAPREDUCE-6762.001.patch
>
>
> This issue was found from a cluster where Pig query occasionally failed on
> NPE. Pig uses JobControl API to track MR job status, but sometimes Job
> History Server failed to flush job meta files to HDFS which caused the status
> update failed. Then we get NPE in
> {{org.apache.hadoop.mapreduce.Job.getJobName}}. The result of this situation
> is quite confusing: Pig query failed, job history is missing, but the job
> status on Yarn is succeed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
