[
https://issues.apache.org/jira/browse/HADOOP-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587522#action_12587522
]
Amareshwari Sriramadasu commented on HADOOP-2403:
-------------------------------------------------
JobHistory parser reads line by line and parses it. If line ends with {b} '\'
{b}, it will continue reading next line.
So, If error messages have more than one line, the lines should be appended
with {b} '\' {b} (except the last line) before writing to log file.
Thoughts?
> JobHistory log files contain data that cannot be parsed by
> org.apache.hadoop.mapred.JobHistory
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-2403
> URL: https://issues.apache.org/jira/browse/HADOOP-2403
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Runping Qi
> Priority: Critical
>
> When some tasks failed, the job tracker writes an line to the history file
> with error message.
> However, the error message may mess up with the history file format, choking
> the history parser. Here is an example:
> MapAttempt TASK_TYPE="MAP" TASKID="tip_200712102254_0001_m_000090"
> TASK_ATTEMPT_ID="task_200712102254_0001_m_000090_0" TASK_STATUS="FAILED"
> FINISH_TIME="1197327293253" HOSTNAME="XXXX:50050"
> ERROR="java.lang.IllegalArgumentException: Trouble to get key or value (<,>
> substituted by null
> . Key XML-Ori:
> <Root>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
