hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5448) JobHistory should use JobTracker's configuration for paths created/read on hadoop.job.history.location
Date Tue, 10 Mar 2009 06:06:50 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680385#action_12680385
] 

Amar Kamat commented on HADOOP-5448:
------------------------------------

Job's configuration is also required for _user-name_, _job-name_ and _user-log-location_.
Does it make sense to fix (finalize) *hadoop.job.history.location* during JobHistory initialization
(JobHistory.init())?

> JobHistory should use JobTracker's configuration for paths created/read on hadoop.job.history.location
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5448
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5448
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Devaraj Das
>
> The JobHistory methods use the user's jobconf to create/read history file paths on both
hadoop.job.history.location and hadoop.job.history.user.location. Even the RecoveryManager
uses the user's jobconf. This should be fixed to use the JobTracker's conf for the history
files on hadoop.job.history.location.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message