[
https://issues.apache.org/jira/browse/YARN-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375807#comment-15375807
]
Karthik Kambatla commented on YARN-5304:
----------------------------------------
I spoke to [~esteban] about this. In his opinion, the minicluster approach
(master, RS etc. in a single process) is discouraged. I am assuming the goal is
to do a pseudo-distributed setup of HBase - Master and RegionServer in
different processes.
> 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: [email protected]
For additional commands, e-mail: [email protected]
