[
https://issues.apache.org/jira/browse/YARN-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343128#comment-15343128
]
Naganarasimha G R commented on YARN-5174:
-----------------------------------------
sorry for the delay [~varun_saxena],
Basically update was to ensure that the timeline client address needs to be
updated even if amrmproxy is not used. And the address will be made available
in the response of AM registration/reheartbeat.
> 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: Hierarchy.png,
> PublishingApplicationDatatoYARNTimelineServicev.pdf, The YARN Timeline
> Service v.2.pdf, YARN-5174-YARN-2928.01.patch, YARN-5174-YARN-2928.02.patch,
> YARN-5174-YARN-2928.03.patch, YARN-5174-YARN-2928.03.patch,
> YARN-5174-YARN-2928.04.patch, YARN-5174-YARN-2928.05.patch,
> YARN-5174-YARN-2928.05.patch, flow_hierarchy.png
>
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
