[
https://issues.apache.org/jira/browse/MAPREDUCE-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949168#comment-13949168
]
Hudson commented on MAPREDUCE-5805:
-----------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #522 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/522/])
MAPREDUCE-5805. Fixed MapReduce JobHistory encoding of queue-name to escape
hyphens and thus avoid parsing errors. Contributed by Akira Ajisaka. (vinodkv:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1582125)
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java
> Unable to parse launch time from job history file
> -------------------------------------------------
>
> Key: MAPREDUCE-5805
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5805
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 2.3.0
> Reporter: Fengdong Yu
> Assignee: Akira AJISAKA
> Fix For: 2.4.0
>
> Attachments: MAPREDUCE-5805.patch
>
>
> when job complete, there are WARN complains in the log:
> {code}
> 2014-03-19 13:31:10,036 WARN
> org.apache.hadoop.mapreduce.v2.jobhistory.FileNameIndexUtils: Unable to parse
> launch time from job history file
> job_1395204058904_0003-1395206473646-root-test_one_word-1395206966214-4-2-SUCCEEDED-root.test-queue-1395206480070.jhist
> : java.lang.NumberFormatException: For input string: "queue"
> {code}
> because there is (-) in the queue name 'test-queue', we split the job
> history file name by (-), and get the ninth item as job start time.
> FileNameIndexUtils.java
> {code}
> private static final int JOB_START_TIME_INDEX = 9;
> {code}
> but there is another potential issue:
> if I also include '-' in the job name(test_one_world in this case), there are
> all misunderstand.
--
This message was sent by Atlassian JIRA
(v6.2#6252)