[
https://issues.apache.org/jira/browse/HADOOP-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556907#action_12556907
]
eric baldeschwieler commented on HADOOP-2178:
---------------------------------------------
I don't think it makes sense to address HADOOP-1876 by storing history on HDFS
by default.
I think it is better to keep the server logs on the local machine by default
and allow a configuration to store them in a well specified place on HDFS.
This will keep a HOD user from creating leavings all over the HDFS, but allow
for alternate uses like HADOOP-1876.
We have 3 use cases we need to think about separately:
1) A cluster with one permanent JT. This should have a single well know place
it logs.
2) A HOD JT, this should send logs to a user specified directory
3) Central logging of job summary data that works in either of the above cases.
We should create a distinct JIRA to discuss this.
> 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.
