hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushil Ks (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-8270) Adding JMX Metrics for Timeline Collector and Reader
Date Fri, 01 Jun 2018 15:32:00 GMT

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

Sushil Ks edited comment on YARN-8270 at 6/1/18 3:31 PM:
---------------------------------------------------------

Hi Haibo, thanks for reviewing please find my comments below,

1) Yes the collector metric is an aggregate for all collectors on the same node i.e on all
NM and RM
 2) Do you mean separate metrics by *TimelineEntityType*? like YARN_APPLICATION, YARN_APPLICATION_ATTEMPT
etc.
 3) My bad its actually private, sure makes sense will make it *update*Metrics()

4) Will add double check inside getInstance() for thread safety.


was (Author: sushil-k-s):
Hi Haibo, thanks for reviewing please find my comments below,

1) Yes the collector metric is an aggregate for all collectors on the same node i.e on all
NM and RM
2) Do you mean separate metrics by *TimelineEntityType*? like YARN_APPLICATION, YARN_APPLICATION_ATTEMPT
etc.
3) My bad its actually private, sure makes sense will make it *update*Metrics()

4) I made use of *double checked locking pattern*  for getInstance() is it still not thread-safe?

> Adding JMX Metrics for Timeline Collector and Reader
> ----------------------------------------------------
>
>                 Key: YARN-8270
>                 URL: https://issues.apache.org/jira/browse/YARN-8270
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: ATSv2, timelineserver
>            Reporter: Sushil Ks
>            Assignee: Sushil Ks
>            Priority: Major
>         Attachments: YARN-8270.001.patch
>
>
> This Jira is for emitting JMX Metrics for ATS v2 Timeline Collector and Timeline Reader,
basically for Timeline Collector it tries to capture success, failure and latencies for *putEntities*
and *putEntitiesAsync*  from *TimelineCollectorWebService* and all the API's success, failure
and latencies for fetching TimelineEntities from *TimelineReaderWebServices*. This would actually
help in monitoring and measuring performance for ATSv2 at scale.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message