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

Naganarasimha G R commented on YARN-3034:
-----------------------------------------

Hi [~zjshen],
bq. According to this comments, it seems that you want to create a separate 
stack to put entities into RMTimelineCollector, right? If so, the current 
design makes sense.
yes I wanted to create a separate stack similar to SystemMetricsPublisher, so 
that ATS V1 and V2 are less coupled and removal of SMP once completely 
deprecated is smoother

bq.  yarn.resourcemanager.system-metrics-publisher.enabled for v1 
SystemMetricsPublisher. For v2, both RM and NM reads 
yarn.system-metrics-publisher.enabled? No need to have v1/v2 flag?
On after thoughts i feel this approach is better as once we deprecate SMP then 
there will be unnecessary additional configuration of which version type, which 
would not be required. If all are fine then will move back to the approach as 
mentioned by Zhijie.

> [Collector wireup] Implement RM starting its timeline collector
> ---------------------------------------------------------------
>
>                 Key: YARN-3034
>                 URL: https://issues.apache.org/jira/browse/YARN-3034
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Naganarasimha G R
>         Attachments: YARN-3034-20150312-1.patch, YARN-3034.20150205-1.patch, 
> YARN-3034.20150316-1.patch, YARN-3034.20150318-1.patch, 
> YARN-3034.20150320-1.patch
>
>
> Per design in YARN-2928, implement resource managers starting their own ATS 
> writers.



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

Reply via email to