[
https://issues.apache.org/jira/browse/MAPREDUCE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832677#action_12832677
]
Edward Capriolo commented on MAPREDUCE-323:
-------------------------------------------
Being able to control the structure better is definitely a nice feature.
Practically, for dividing the job folders by mm/dd/yy would solve the immediate
problem on having to clean and restart your JobTracker when you hit ext3 limit.
Introducing a variable into the jobtracker mapred.jobhistory.maxjobhistory and
a FIFO queue might be helpful as well. As things stand now a downtime and
cleanup is needed to keep the JobTracker running well, this is less then
optimal.
> Improve the way job history files are managed
> ---------------------------------------------
>
> Key: MAPREDUCE-323
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-323
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Amar Kamat
> Assignee: Amareshwari Sriramadasu
> Priority: Critical
>
> Today all the jobhistory files are dumped in one _job-history_ folder. This
> can cause problems when there is a need to search the history folder
> (job-recovery etc). It would be nice if we group all the jobs under a _user_
> folder. So all the jobs for user _amar_ will go in _history-folder/amar/_.
> Jobs can be categorized using various features like _jobid, date, jobname_
> etc but using _username_ will make the search much more efficient and also
> will not result into namespace explosion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
