[
https://issues.apache.org/jira/browse/MAPREDUCE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852395#action_12852395
]
Steve Loughran commented on MAPREDUCE-1100:
-------------------------------------------
OK, so what do you want here? I could +1 MAPREDUCE-1057 and if hudson is happy,
push out to 0.21/0.22 branches. MAPREDUCE-1100 would be the patch that goes
into trunk.
The other fix would be documentation. I've added something on logging to
[http://wiki.apache.org/hadoop/DiskSetup] but it could be improved. More
subtly, any production cluster that doesn't have a limit on log size is doomed.
Some preflight checks could note this and perhaps warn.
> 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, MAPREDUCE-1100-20091216.2.txt,
> patch-1100-fix-ydist.2.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.
