High Level Steps
=================

1. Download Apache Hadoop and install.
2. Download Hbase and install

Note: 

* No need to install separate zookeeper. Hadoop has built-in zookeeper
  built-into NameNode.

Installing Hadoop
===================

Use core-site.xml like below::

  <configuration>
    <property>
     <name>fs.defaultFS</name>
     <value>hdfs://localhost:9000</value>
    </property>
    <property>
     <name>hadoop.tmp.dir</name>
     <value>/home/hdfs/hadoop-tmp-dir</value>
    </property>
  </configuration>


Use hdfs-site.xml like the following::

  <configuration>
     <property>
            <name>dfs.replication</name>
            <value>1</value>
    </property>

    <property>
            <name>dfs.namenode.rpc-bind-host</name>
            <value>0.0.0.0</value>
    </property>
     <property>
            <name>dfs.datanode.data.dir</name>
            <value>file:///home/hdfs/base/dfs/data</value>
    </property>
     <property>
            <name>dfs.namenode.name.dir</name>
            <value>file:///home/hdfs/base/dfs/name</value>
    </property>
  </configuration>


Note: Name node uses default service port number that is 8030 or 9000 or whatever.
      If you use fs.defaultFS a.k.a fs.default.name property then you can force 
      specific port.

Installing Hbase
=================

hbase-env.sh
--------------

Edit conf/hbase-env.sh to uncomment the following line:

export HBASE_MANAGES_ZK=true

Above causes Hbase to run/manage it's own zookeeper.

hbase-site.xml
----------------

<configuration>

  <property>
      <name>hbase.rootdir</name>
      <value>hdfs://localhost:9000/hbase</value>
    <description>
        This should match with hadoop hdfs fs.default.name or fs.defaultFS port.
    </description>
  </property>

  <property>
      <name>hbase.zookeeper.property.dataDir</name>
        <value>/home/hbase/hbase-zookeeper-data</value>
  </property>

  <property>
      <name>hbase.cluster.distributed</name>
      <value>true</value>
  </property>

<property>
      <name>hbase.zookeeper.quorum</name>
      <value>localhost</value>
      <description> Also see If HBASE_MANAGES_ZK is set in hbase-env.sh </description>
</property>

<property>
    <name>hbase.zookeeper.property.clientPort</name>
    <value>2181</value>
    <description> default is 2181 </description>
</property>
<property>
    <name>hbase.master</name>
    <value>localhost:60000</value>
    <description>The host and port that the HBase master runs at. 
                 default is 60000 </description>
  </property>
 
  <property>
    <name>hbase.tmp.dir</name>
    <value>/home/hbase/hbase-tmp-dir</value>
  </property>

<property>
      <name>zookeeper.znode.parent</name>
      <value>/hbase</value>
</property>

<property>
      <name>hbase.master.ipc.address</name>
      <value>0.0.0.0</value>
</property>
<property>
      <name>hbase.regionserver.ipc.address</name>
      <value>0.0.0.0</value>
</property>

<property>
    <name>hbase.unsafe.stream.capability.enforce</name>
    <value>false</value>
    <description>

      Set to false for standalone mode. Must be true for hdfs.
      Controls whether HBase will check for stream capabilities (hflush/hsync).
      Disable this if you intend to run on LocalFileSystem, denoted by a rootdir
      with the 'file://' scheme, but be mindful of the NOTE below.

      WARNING: Setting this to false blinds you to potential data loss and
      inconsistent system state in the event of process and/or node failures. If
      HBase is complaining of an inability to use hsync or hflush it's most
      likely not a false positive.
    </description>
</property>

<property>
  <name>hbase.table.sanity.checks</name>
  <value>false</value>
</property>

</configuration>