Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 13 May 2017 00:36:04 +0000 (UTC)
From: "Carlo Curino (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13066893.1493164610000.202260.1494635764958@Atlassian.JIRA>
In-Reply-To: <JIRA.13066893.1493164610000@Atlassian.JIRA>
References: <JIRA.13066893.1493164610000@Atlassian.JIRA> <JIRA.13066893.1493164610310@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6528) Add JMX metrics for Plan Follower
 and Agent Placement and Plan Operations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 13 May 2017 00:36:11 -0000


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

Carlo Curino commented on YARN-6528:
------------------------------------

hi [~seanpo03] thanks for the updated patch.

Regarding (3): I think the roll-up at "root" level should provide what you have as a global metric, correct? The cost of storing is a little hire, but since our hierarchies are usually not too deep, shouldn't be too bad.
Regarding (4): I understand, but again, I would like to see it group-by queue, as I think this provides better visibility.

I would encourage you to take YARN-6528 and "merge" it with your effort, we can mark one of the two patches as duplicate. Basically I would follow the structure of YARN-6528 for queue-level metrics, but use your more rich set of metrics to track. 
Does this make sense?

> Add JMX metrics for Plan Follower and Agent Placement and Plan Operations
> -------------------------------------------------------------------------
>
>                 Key: YARN-6528
>                 URL: https://issues.apache.org/jira/browse/YARN-6528
>             Project: Hadoop YARN
>          Issue Type: Task
>            Reporter: Sean Po
>            Assignee: Sean Po
>         Attachments: YARN-6528.v001.patch, YARN-6528.v002.patch, YARN-6528.v003.patch
>
>
> YARN-1051 introduced a ReservationSytem that enables the YARN RM to handle time explicitly, i.e. users can now "reserve" capacity ahead of time which is predictably allocated to them. In order to understand in finer detail the performance of Rayon, YARN-6528 proposes to include JMX metrics in the Plan Follower, Agent Placement and Plan Operations components of Rayon.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org