[jira] [Commented] (YARN-5304) Ship single node HBase config option with single startup command

["Vrushali C (JIRA)" <ji...@apache.org>]

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

Vrushali C commented on YARN-5304:
----------------------------------

Went over this jira with [~jrottinghuis] and here is a summary of what we discussed:

- Provide a default hbase site via timeline service (perhaps called hbase-site-timelineservice.xml) which can be used to start up a single node hbase setup 
- ask the user to set HBASE_HOME to point to where the hbase installation is
- ask the user to set yarn.timeline-service.hbase.configuration.file config param to where the hbase-site-timelineservice.xml is located 
- ask the user to ensure that hbase is set up on a node which is in the ZK quorum setting in the config for the clients to be able to connect to this cluster. it could be the node as yarn.timeline-service.hostname or it could be a node like RM.
- ask the user to ensure that hbase clients have this yarn.timeline-service.hbase.configuration.file in their classpath.
- Provide a set of steps so that a user can start up / stop a single node hbase cluster (ensuring that the NN address is in the hbase root dir setting). 
- Also, ensure that it's clear that some steps are one-time only, like copying the jars for coprocessor and creating the schema. They need not be done each time the cluster is started/stopped/restarted. 

The steps should be made as clear as we can make them. The idea is that these steps should be such that users can just copy/paste these commands (with minimal, clearly explained variable modifications) and run them. 


> 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: Vrushali C
>              Labels: YARN-5355, yarn-5355-merge-blocker
>
> 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org