[
https://issues.apache.org/jira/browse/YARN-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335410#comment-15335410
]
Joep Rottinghuis commented on YARN-5265:
----------------------------------------
Contemplating what is better in FlowScanner
line 104:
{code}
Configuration hbaseConf = env.getConfiguration();
{code}
or
{code}
Configuration hbaseConf =
TimelineStorageUtils.getTimelineServiceHBaseConf(env.getConfiguration();
{code}
I think the former (existing code) may be better because this is a yarn config,
which should be picked up from yarn-site.xml and not be overwritten by a level
of indirection from a hbase-site.xml.
> Make HBase configuration for the timeline service configurable
> --------------------------------------------------------------
>
> Key: YARN-5265
> URL: https://issues.apache.org/jira/browse/YARN-5265
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Joep Rottinghuis
> Assignee: Joep Rottinghuis
> Attachments: ATS v2 cluster deployment v1.png,
> YARN-5265-YARN-2928.01.patch
>
>
> Currently we create "default" HBase configurations, this works as long as the
> user places the appropriate configuration on the classpath.
> This works fine for a standalone Hadoop cluster.
> However, if a user wants to monitor an HBase cluster and has a separate ATS
> HBase cluster, then it can become tricky to create the right classpath for
> the nodemanagers and still have tasks have their separate configs.
> It will be much easier to add a yarn configuration to let cluster admins
> configure which HBase to connect to to write ATS metrics to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
