[
https://issues.apache.org/jira/browse/YARN-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128877#comment-14128877
]
Vinod Kumar Vavilapalli commented on YARN-2033:
-----------------------------------------------
Looks mostly good. Rename yarn.resourcemanager.metrics-publisher.enabled ->
also to say system-metrics-publisher too? Similarly rename
yarn.resourcemanager.metrics-publisher.dispatcher.pool-size?
> Investigate merging generic-history into the Timeline Store
> -----------------------------------------------------------
>
> Key: YARN-2033
> URL: https://issues.apache.org/jira/browse/YARN-2033
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Zhijie Shen
> Attachments: ProposalofStoringYARNMetricsintotheTimelineStore.pdf,
> YARN-2033.1.patch, YARN-2033.10.patch, YARN-2033.2.patch, YARN-2033.3.patch,
> YARN-2033.4.patch, YARN-2033.5.patch, YARN-2033.6.patch, YARN-2033.7.patch,
> YARN-2033.8.patch, YARN-2033.9.patch, YARN-2033.Prototype.patch,
> YARN-2033_ALL.1.patch, YARN-2033_ALL.2.patch, YARN-2033_ALL.3.patch,
> YARN-2033_ALL.4.patch
>
>
> Having two different stores isn't amicable to generic insights on what's
> happening with applications. This is to investigate porting generic-history
> into the Timeline Store.
> One goal is to try and retain most of the client side interfaces as close to
> what we have today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
