[
https://issues.apache.org/jira/browse/MAPREDUCE-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851423#action_12851423
]
Ravi Gummadi commented on MAPREDUCE-1100:
-----------------------------------------
logSize not set in JvmEnv's constructor is tracked in MAPREDUCE-1057. See my
comment(on 22/Oct/09 10:52 AM) at MAPREDUCE-1057 about the issue of "tail -c"
is being done after writing of log.index file is finished. So the issue of
making mapred.userlog.limit.kb work is still open for investigation even with
my patch available at MAPREDUCE-1057.
> 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.
