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 "Rohith Sharma K S (JIRA)" <ji...@apache.org> on 2019/01/28 05:45:00 UTC
[jira] [Commented] (YARN-8270) Adding JMX Metrics for Timeline
Collector and Reader
[ https://issues.apache.org/jira/browse/YARN-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753714#comment-16753714 ]
Rohith Sharma K S commented on YARN-8270:
-----------------------------------------
In branch-3.1, this was causing error while publishing events from NodeManager. The reason is HADOOP-15657 was't present in branch-3.1. I have reverted this change for unblocking release 3.1.2.
Updated the 'Fix Version'!
> 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
> Fix For: 3.2.0, 3.1.2
>
> Attachments: YARN-8270.001.patch, YARN-8270.002.patch, YARN-8270.003.patch, YARN-8270.004.patch, YARN-8270.005.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 and failure latencies for *putEntities* and *putEntitiesAsync* from *TimelineCollectorWebService* , similarly all the API's success and failure 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