[
https://issues.apache.org/jira/browse/MAPREDUCE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768579#action_12768579
]
Hemanth Yamijala commented on MAPREDUCE-1090:
---------------------------------------------
Since this is a log line, I have not included test cases in the patch. But I
manually tested this patch with the following tests:
- Ran a sleep job with a huge sleep time. While the job ran, looked at the
tasktracker logs to see that the values were coming correctly.
- Ran a sleep job with a modified limit. While the job ran, verified the
changed limit parameter was printed in the logs.
Can someone please review ?
> Modify log statement in Tasktracker log related to memory monitoring to
> include attempt id.
> -------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1090
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1090
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.20.1
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Attachments: MAPREDUCE-1090.patch
>
>
> Currently the TaskMemoryManagerThread logs a line like:
> org.apache.hadoop.mapred.TaskMemoryManagerThread: Memory usage of ProcessTree
> 14321 :372686848bytes. Limit : 2147483648bytes.
> It would be very useful to include the Task attempt id for the process tree
> mentioned in the log statement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
