You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2016/04/02 02:14:25 UTC

[jira] [Commented] (YARN-4878) Expose scheduling policy and max running apps over JMX for Yarn queues

    [ https://issues.apache.org/jira/browse/YARN-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222581#comment-15222581 ] 

Karthik Kambatla commented on YARN-4878:
----------------------------------------

Thanks for adding these, Yufei. Comments on the patch:
# FSQueue constructor: instead of creating a new AllocationConfiguration, use {{scheduler.allocConf}}. You probably don't need another local variable either. 
# Why do we need to set the metrics in both QueueManager and FSQueue? 

> Expose scheduling policy and max running apps over JMX for Yarn queues
> ----------------------------------------------------------------------
>
>                 Key: YARN-4878
>                 URL: https://issues.apache.org/jira/browse/YARN-4878
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: yarn
>    Affects Versions: 2.9.0
>            Reporter: Yufei Gu
>            Assignee: Yufei Gu
>         Attachments: YARN-4878.001.patch
>
>
> There are two things that are not currently visible over JMX: the current scheduling policy for a queue, and the number of max running apps. It would be great if these could be exposed over JMX as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)