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] [Commented] (YARN-5304) Ship single node HBase config option with single startup command
Date Fri, 22 Jul 2016 21:27:20 GMT

    [ https://issues.apache.org/jira/browse/YARN-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390217#comment-15390217
] 

Joep Rottinghuis commented on YARN-5304:
----------------------------------------

The goal is the simplest possible setup, but not any simpler.

[~stack] you mentioned we could consider filing an HBase jira to make MiniHBaseCluster persist
files to HDFS rather than just local storage. One challenge with that is that this class,
and its MiniHBaseClusterRegionServer and SingleFileSystemShutdownThread subclasses, sit in
src/test/java directory and hence gets packaged in hbase-server-X.Y.Z-tests.jar

It seems that does leave us with the approach of a setup with 3 JVMs getting launched, even
in the simplest setup: 1 for the Master, 1 for the RegionServer, 1 for ZK.

> Ship single node HBase config option with single startup command
> ----------------------------------------------------------------
>
>                 Key: YARN-5304
>                 URL: https://issues.apache.org/jira/browse/YARN-5304
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Joep Rottinghuis
>            Assignee: Joep Rottinghuis
>              Labels: YARN-5355
>
> For small to medium Hadoop deployments we should make it dead-simple to use the timeline
service v2. We should have a single command to launch and stop the timelineservice back-end
for the default HBase implementation.
> A default config with all the values should be packaged that launches all the needed
daemons (on the RM node) with a single command with all the recommended settings.
> Having a timeline admin command, perhaps an init command might be needed, or perhaps
the timeline service can even auto-detect that and create tables, deploy needed coprocessors
etc.
> The overall purpose is to ensure nobody needs to be an HBase expert to get this going.
For those cluster operators with HBase experience, they can choose their own more sophisticated
deployment.



--
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