[ 
https://issues.apache.org/jira/browse/HBASE-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701752#action_12701752
 ] 

Andrew Purtell commented on HBASE-1173:
---------------------------------------

Yes I think this can make it. How about something along the lines of:

* Use ssh to retrieve hadoop-site.xml and parse for root FS URI, or ask
    ** Use 'hadoop fs' to check validity

* Ask about ZK particulars
    ** Self manage or use existing installation
        *** Existing installation details 

* Ask for master DNS name
    ** Check resolution sanity
    ** Check reachability
    ** Test auto-ssh
    ** Use 'cat /proc/cpu' to check for minimum CPU for master and warn if not
    ** Ask about heap size and enforce minimum requirement
    ** Use 'free' to check for minimum RAM for master and warn if not

* Ask for HRS DNS names
    ** Check resolution sanity
    ** Check reachability
    ** Test auto-ssh
    ** Use 'cat /proc/cpu' to check for minimum CPU and warn if not
    ** Ask about heap size and enforce minimum requirement
    ** Use 'free' to check for minimum RAM and warn if not

* Ask to make xceivers change to hadoop-site.xml. Ballpark it according to 
'free' output.

* Write 'zoo.cfg', 'hbase-env.sh', 'hbase-site.xml', 'regionservers' and use 
scp to push them out. 

* Parse and update 'hadoop-site.xml' and use scp to push out the modified 
version.

* Use ssh to symlink 'hadoop-site.xml' into hbase/conf/

For each question, provide some explanatory text. Provide a reasonable "don't 
care" or "don't know" default.

Some small changes to bin/hbase are necessary to support separate -Xmx options 
for various daemon types.

Should we do more?


> HBase configuration wizard
> --------------------------
>
>                 Key: HBASE-1173
>                 URL: https://issues.apache.org/jira/browse/HBASE-1173
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>             Fix For: 0.20.0
>
>
> There are some aspects of HBase configuration that will be daunting for new 
> users. For example, Zookeeper configuration needs to list all hosts so it can 
> determine quorum. New users won't necessarily even understand the distinction 
> between HBase and Zookeeper.  Let's produce a bash configuration wizard that 
> can generate all necessary config files or file edits based on the answers 
> provided to a few simple questions. This will allow neophytes to quickly spin 
> up clusters correctly without duplicating common errors. Advanced 
> configuration is out of scope for this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to