hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joep Rottinghuis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5265) Make HBase configuration for the timeline service configurable
Date Fri, 17 Jun 2016 04:43:05 GMT

     [ https://issues.apache.org/jira/browse/YARN-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joep Rottinghuis updated YARN-5265:
-----------------------------------
    Attachment: YARN-5265-YARN-2928.01.patch

YARN-5265-YARN-2928.01.patch: Untested initial outline of what I think might work.
Need to do manual testing and come up with a good way to create a unit test for this.
I'm still considering if we want to use the same approach in the Coprocessor. It would probably
not be needed, as the only cluster where those are deployed will be on the HBase cluster hosting
the timeline service tables.
I might still add it so that folks can choose to have separate config variables (timeouts
etc) for the timeline coprocessors than for other ones.
This also reminds me that we should update the documentation to clarify that the yarn.timeline-service.hbase.coprocessor.app-final-value-retention-milliseconds
value needs to be present in the config on the region server.

> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message