[jira] Created: (HADOOP-2403) JobHistory log files contain data that cannot be parsed by org.apache.hadoop.mapred.JobHistory

View: New views
2 Messages — Rating Filter:   Alert me  

[jira] Created: (HADOOP-2403) JobHistory log files contain data that cannot be parsed by org.apache.hadoop.mapred.JobHistory

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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
          Issue Type: Bug
          Components: mapred
            Reporter: Runping Qi



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.


[jira] Updated: (HADOOP-2403) JobHistory log files contain data that cannot be parsed by org.apache.hadoop.mapred.JobHistory

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


     [ https://issues.apache.org/jira/browse/HADOOP-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mac Yang updated HADOOP-2403:
-----------------------------

       Priority: Critical  (was: Major)
    Description:
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>


  was:

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>



> 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
>          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.