Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-6096

SummarizedJob class NPEs with some jhist files

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      When I Parse the JobHistory in the HistoryFile,I use the Hadoop System's map-reduce-client-core project org.apache.hadoop.mapreduce.jobhistory.JobHistoryParser class and HistoryViewer$SummarizedJob to Parse the JobHistoryFile(Just Like job_1408862281971_489761-1410883171851_XXX.jhist)
      and it throw an Exception Just Like
      Exception in thread "pool-1-thread-1" java.lang.NullPointerException
      at org.apache.hadoop.mapreduce.jobhistory.HistoryViewer$SummarizedJob.<init>(HistoryViewer.java:626)
      at com.jd.hadoop.log.parse.ParseLogService.getJobDetail(ParseLogService.java:70)

      After I'm see the SummarizedJob class I find that attempt.getTaskStatus() is NULL , So I change the order of
      attempt.getTaskStatus().equals (TaskStatus.State.FAILED.toString()) to
      TaskStatus.State.FAILED.toString().equals(attempt.getTaskStatus())
      and it works well .

      So I wonder If we can change all attempt.getTaskStatus() after TaskStatus.State.XXX.toString() ?

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            piaoyu zhang zhangyubiao Assign to me
            piaoyu zhang zhangyubiao

            Dates

              Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 0.5h
              0.5h

              Slack

                Issue deployment