[
https://issues.apache.org/jira/browse/HADOOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556625#action_12556625
]
Devaraj Das commented on HADOOP-2178:
-------------------------------------
+1 on Eric's suggestion. The jobhistory viewer (web server with the job history
related JSPs) can take the output directory as the input and populate the
history datastructures. This can be on a per-user basis for now (e.g.,
bin/hadoop jobhistoryview -output <dir> .. ), and, in the future, we could make
the viewer a centralized web-enabled server that anyone can use. Thoughts?
bq. The output data may be deleted anytime when it is no longer needed. The log
data may be needed long after the output data is deleted.
As Eric suggested, this can be solved by allowing the user to move the files to
some persistent location...
> Job history on HDFS
> -------------------
>
> Key: HADOOP-2178
> URL: https://issues.apache.org/jira/browse/HADOOP-2178
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Reporter: Amareshwari Sri Ramadasu
> Assignee: Amareshwari Sri Ramadasu
> Fix For: 0.16.0
>
>
> This issue addresses the following items :
> 1. Check for accuracy of job tracker history logs.
> 2. After completion of the job, copy the JobHistory.log(Master index file)
> and the job history files to the DFS.
> 3. User can load the history with commands
> bin/hadoop job -history <directory>
> or
> bin/hadoop job -history <jobid>
> This will start a stand-alone jetty and load jsps
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
