[
https://issues.apache.org/jira/browse/MAPREDUCE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774921#action_12774921
]
Vinod K V commented on MAPREDUCE-1100:
--------------------------------------
I would like to point one fine point with the above implementation:
bq. removeOldFilesToControlCumulativeUsage(); // remove very old logs if total
usage is alarming irrespective of retain.hours
With the above, retain.hours is no longer a proper contract for tasks, logs can
get cleaned-up at arbitrary times. So the 4th requirement is broken -
bq. (4) Clean up of a particular task's user logs should be deterministic -
users should have an idea of how long they can see their logs.
The only way I think of in which this can be addressed is by taking care of the
cumulative disk-usage of TaskTracker while scheduling a new task. Should this
be done too?
> User's task-logs filling up local disks on the TaskTrackers
> -----------------------------------------------------------
>
> Key: MAPREDUCE-1100
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1100
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.21.0
> Reporter: Vinod K V
> Assignee: Vinod K V
> Attachments: MAPREDUCE-1100-20091102.txt, MAPREDUCE-1100-20091106.txt
>
>
> Some user's jobs are filling up TT disks by outrageous logging.
> mapreduce.task.userlog.limit.kb is not enabled on the cluster. Disks are
> getting filled up before task-log cleanup via
> mapred.task.userlog.retain.hours can kick in.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
