You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/22 20:50:40 UTC

[jira] [Resolved] (MAPREDUCE-700) Too many copies of job-conf with the jobtracker

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

Allen Wittenauer resolved MAPREDUCE-700.
----------------------------------------

    Resolution: Fixed

Lots of changes here already. Closing this as stale.

> Too many copies of job-conf with the jobtracker
> -----------------------------------------------
>
>                 Key: MAPREDUCE-700
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-700
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>
> As of today the jobtracker has job-conf copies in
> # mapred.system.dir : created while job-submission 
> # jobtracker-subdir (created by JobInProgress upon creation)
> # log-dir : created upon job-init
> # history-dir : created upon job-init
> Its difficult to manage these conf files. The problem aggravates under restart.



--
This message was sent by Atlassian JIRA
(v6.2#6252)