[
https://issues.apache.org/jira/browse/MAPREDUCE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated MAPREDUCE-1808:
-----------------------------------
Status: Open (was: Patch Available)
Cancelling patch since it no longer applies.
Alex: it seems to me that this use case might be better suited by analyzing
history logs, but I'm not entirely against it.
I noticed lots of watchers on the ticket - do others have some thoughts about
this idea?
> Have a configurable metric reporting CPU/disk usage per user
> ------------------------------------------------------------
>
> Key: MAPREDUCE-1808
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1808
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: tasktracker
> Reporter: Alex Kozlov
> Assignee: Alex Kozlov
> Attachments: HADOOP-6755.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Many organizations are looking at resource usage per department/group/user
> for diagnostic and resource allocation purposes. It should be
> straightforward to implement a metric showing the simple resource usage like
> CPU time and disk I/O per user and aggregate them using Ganglia.
> Eventually, we can create an API for pluggable metrics (there is one for
> Jobtracker and Tasktracker).
> Let me know your thoughts.
> Alex K
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
