hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-130) Delete the jobconf copy from the log directory of the JobTracker when the job is retired
Date Fri, 03 Jul 2009 04:24:47 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726786#action_12726786
] 

Amar Kamat commented on MAPREDUCE-130:
--------------------------------------

Upon restart the new jobtracker has no idea about the old completed jobs. I have opened MAPREDUCE-700
to address this. One solution is to have just one copy of jobconf with the jobtracker and
delete it upon restart or job expiry. The ideal place to have it is the jobtracker subdir
which gets cleaned up upon restart. 

> Delete the jobconf copy from the log directory of the JobTracker when the job is retired
> ----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-130
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-130
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Devaraj Das
>            Assignee: Amar Kamat
>             Fix For: 0.20.1
>
>         Attachments: HADOOP-5995-v1.0.patch, HADOOP-5995-v1.1.patch, MAPREDUCE-130-v1.0-branch-0.20.patch,
MAPREDUCE-130-v1.0.patch
>
>
> The JobTracker (for web-ui viewing purposes), copies the jobconf from the hdfs and store
it in the log directory. The file should be deleted when the job is retired (removed from
memory).

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