[
https://issues.apache.org/jira/browse/YARN-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008682#comment-16008682
]
Sean Po commented on YARN-6528:
-------------------------------
Thanks [~curino] for the comments. I'll fix 1 and 2 in the next iteration.
3. I think both can exist. Monitoring a single metric for abrupt changes to
determine the system health is useful for automated alerts and watchdogs.
Having metrics be posted on a per-plan basis is useful for users of the
particular plan, as well as for administrators of the plan to determine if the
system is in bad shape. What are your thoughts on this topic?
4. The rationale for keeping both the agent and plan metrics is to make it
easier to determine the component responsible for a possible agent operation
performance degradation. In addition, future agents may contain heavier
placement logic, and it will be useful to have benchmark metrics to compare the
agent metrics to.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
