You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/02/13 04:28:57 UTC
[jira] Commented: (MAPREDUCE-2323) Add metrics to the fair
scheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994016#comment-12994016 ]
Todd Lipcon commented on MAPREDUCE-2323:
----------------------------------------
Would appreciate feedback on the following:
- is the locking correct for updateMetrics? I take a lock on the scheduler and then the poolmanager, but no other locks.
- could it be finer grain? (do I need the coarse scheduler lock at all? unclear)
- should I add a configuration to disable the job-level metrics and only use pool-level metrics?
- when a user pool becomes empty, should we remove its metrics records?
> Add metrics to the fair scheduler
> ---------------------------------
>
> Key: MAPREDUCE-2323
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2323
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: contrib/fair-share
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 0.23.0
>
> Attachments: mr-2323-20.txt
>
>
> It would be useful to be able to monitor various metrics in the fair scheduler, like demand, fair share, min share, and running task count.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira