[
https://issues.apache.org/jira/browse/YARN-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325358#comment-15325358
]
Sangjin Lee commented on YARN-5174:
-----------------------------------
Thanks [~gtCarrera9] for the great content!
Just so I understand, your proposal is to restructure and expand the existing
{{TimelineServiceV2.html}} to include this content, right? There seems to be a
fair amount of overlap with this doc and the existing doc, and I wanted to make
sure we're on the same page.
The content looks good to me for the most part. If I have to nitpick one,
bq. Each metric item contains metric name (id), value, and what kind of
aggregation operation should be performed in this metric (noop by default).
I am not sure if we need to highlight the aggregation operation bit. First of
all, this is only about the *application* aggregation. Also, user code should
normally post the application-level metrics directly onto the application
entity (e.g. MR AM writing job metrics on the application entity). Should we
simply drop the mention of the aggregation op part?
> several updates/corrections to timeline service documentation
> -------------------------------------------------------------
>
> Key: YARN-5174
> URL: https://issues.apache.org/jira/browse/YARN-5174
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Labels: yarn-2928-1st-milestone
> Attachments: PublishingApplicationDatatoYARNTimelineServicev.pdf
>
>
> One part that is missing in the documentation is the need to add
> {{hbase-site.xml}} on the client side (the client hadoop cluster). First, we
> need to arrive at the minimally required client setting to connect to the
> right hbase cluster. Then, we need to document it so that users know exactly
> what to do to configure the cluster to use the timeline service v.2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
