[
https://issues.apache.org/jira/browse/HADOOP-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648652#action_12648652
]
Doug Cutting commented on HADOOP-4670:
--------------------------------------
> The type of search we do there is given a jobtracker-hostname, job-id,
> username and job-name [...]
Thanks for the explanation. In that case, a directory per username probably
does make sense. Really big directories are generally cumbersome, so you might
still also slice things by date too, either above or below the username, so
that even a user who has run lots of jobs won't cause, e.g., huge RPCs for
listings.
> Improve the way job history files are managed
> ---------------------------------------------
>
> Key: HADOOP-4670
> URL: https://issues.apache.org/jira/browse/HADOOP-4670
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Fix For: 0.20.0
>
>
> 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.
