最近一直在考慮統計分析的基礎資料、中間資料、結果資料該怎麼存放才有利於寫入、讀取、彙總了，Mysql當然是不二人選，不過涉及到更新的時候，都要先select後update，效率比較低，另外一個就是不同維度的統計資料要是排序的話，那就慘了，到處都是索引，整一張表就是各種索引了，又導致寫入變得更加慢，當然有很多辦法可以加速這個過程，也是可以信賴的，不過總不甘心，想試一試是否有更好辦法了！這時hbase自然出現了，天然的和Hadoop在一塊，有基礎維度後就可以計算出各種其它不同的維度，各種維度計算還是可以重複進行的，統計資料本就是一個維度+資料這樣的結果，剛好就是key/value了，如果需要支援value排序的話，也可以完美解決！遂想，好歹先試一試了，這不才有如下這個實驗了！

Hadoop環境：

hadoop2.2.0 +HA(QJM)，4節點

Hbase環境：

hbase-0.98.3-hadoop2(安裝目錄：/home/hadoop/hbase-0.98.3-hadoop2），4個節點(hadoop25\hadoop28\hadoop201\hadoop224)

ZK環境：

三節點的獨立的ZK叢集（ZK25、ZK28、ZK224，clientPort為2181)

以下為具體安裝Hbase-0.98.3那些事！

我有現成已經搭建好，可以穩定執行的Hadoop2.2.0+HA(QJM)的環境，搭建hbase其實很容易的（測試而已，所以要求也不高）。

1、下載hbase-0.98.3-hadoop2-bin.tar.gz

直接從http://hbase.apache.org下載最新的穩定版本hbase-0.98.3-hadoop2，這個版本預設支援的就是hadoop2.2.0，所以省了好些麻煩事。

2、配置那點事

（1）修改hadoop2.2.0的配置檔案hdfs-site.xml（增加支援append和增大開啟檔案的個數限制）

     <property>
        <name>dfs.datanode.max.xcievers</name>
        <value>4096</value>
     </property>
     <property> 
        <name>dfs.support.append</name> 
        <value>true</value> 
     </property>
 

這個配置修改了，需要把Hadoop叢集重啟。（我

#
#/**
# * Copyright 2007 The Apache Software Foundation
# *
# * Licensed to the Apache Software Foundation (ASF) under one
# * or more contributor license agreements.  See the NOTICE file
# * distributed with this work for additional information
# * regarding copyright ownership.  The ASF licenses this file
# * to you under the Apache License, Version 2.0 (the
# * "License"); you may not use this file except in compliance
# * with the License.  You may obtain a copy of the License at
# *
# *     http://www.apache.org/licenses/LICENSE-2.0
# *
# * Unless required by applicable law or agreed to in writing, software
# * distributed under the License is distributed on an "AS IS" BASIS,
# * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# * See the License for the specific language governing permissions and
# * limitations under the License.
# */


# Set environment variables here.


# This script sets variables multiple times over the course of starting an hbase process,
# so try to keep things idempotent unless you want to take an even deeper look
# into the startup scripts (bin/hbase, etc.)


# The java implementation to use.  Java 1.6 required.
export JAVA_HOME=/home/hadoop/jdk1.7.0_45


# Extra Java CLASSPATH elements.  Optional.
# export HBASE_CLASSPATH=


# The maximum amount of heap to use, in MB. Default is 1000.
export HBASE_HEAPSIZE=1024


# Extra Java runtime options.
# Below are what we set by default.  May only work with SUN JVM.
# For more on why as well as other possible settings,
# see http://wiki.apache.org/hadoop/PerformanceTuning
export HBASE_OPTS="-XX:+UseConcMarkSweepGC"


# Uncomment one of the below three options to enable java garbage collection logging for the server-side processes.


# This enables basic gc logging to the .out file.
# export SERVER_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps"


# This enables basic gc logging to its own file.
# If FILE-PATH is not replaced, the log file(.gc) would still be generated in the HBASE_LOG_DIR .
# export SERVER_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:<FILE-PATH>"


# This enables basic GC logging to its own file with automatic log rolling. Only applies to jdk 1.6.0_34+ and 1.7.0_2+.
# If FILE-PATH is not replaced, the log file(.gc) would still be generated in the HBASE_LOG_DIR .
# export SERVER_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:<FILE-PATH> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=1 -XX:GCLogFileSize=512M"


# Uncomment one of the below three options to enable java garbage collection logging for the client processes.


# This enables basic gc logging to the .out file.
# export CLIENT_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps"


# This enables basic gc logging to its own file.
# If FILE-PATH is not replaced, the log file(.gc) would still be generated in the HBASE_LOG_DIR .
# export CLIENT_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:<FILE-PATH>"


# This enables basic GC logging to its own file with automatic log rolling. Only applies to jdk 1.6.0_34+ and 1.7.0_2+.
# If FILE-PATH is not replaced, the log file(.gc) would still be generated in the HBASE_LOG_DIR .
# export CLIENT_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -Xloggc:<FILE-PATH> -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=1 -XX:GCLogFileSize=512M"


# Uncomment below if you intend to use the EXPERIMENTAL off heap cache.
# export HBASE_OPTS="$HBASE_OPTS -XX:MaxDirectMemorySize="
# Set hbase.offheapcache.percentage in hbase-site.xml to a nonzero value.




# Uncomment and adjust to enable JMX exporting
# See jmxremote.password and jmxremote.access in $JRE_HOME/lib/management to configure remote password access.
# More details at: http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
#
# export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
# export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10101"
# export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10102"
# export HBASE_THRIFT_OPTS="$HBASE_THRIFT_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10103"
# export HBASE_ZOOKEEPER_OPTS="$HBASE_ZOOKEEPER_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10104"
# export HBASE_REST_OPTS="$HBASE_REST_OPTS $HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=10105"


# File naming hosts on which HRegionServers will run.  $HBASE_HOME/conf/regionservers by default.
# export HBASE_REGIONSERVERS=${HBASE_HOME}/conf/regionservers


# Uncomment and adjust to keep all the Region Server pages mapped to be memory resident
#HBASE_REGIONSERVER_MLOCK=true
#HBASE_REGIONSERVER_UID="hbase"


# File naming hosts on which backup HMaster will run.  $HBASE_HOME/conf/backup-masters by default.
# export HBASE_BACKUP_MASTERS=${HBASE_HOME}/conf/backup-masters


# Extra ssh options.  Empty by default.
# export HBASE_SSH_OPTS="-o ConnectTimeout=1 -o SendEnv=HBASE_CONF_DIR"


# Where log files are stored.  $HBASE_HOME/logs by default.
# export HBASE_LOG_DIR=${HBASE_HOME}/logs


# Enable remote JDWP debugging of major HBase processes. Meant for Core Developers 
# export HBASE_MASTER_OPTS="$HBASE_MASTER_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8070"
# export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8071"
# export HBASE_THRIFT_OPTS="$HBASE_THRIFT_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8072"
# export HBASE_ZOOKEEPER_OPTS="$HBASE_ZOOKEEPER_OPTS -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8073"


# A string representing this instance of hbase. $USER by default.
# export HBASE_IDENT_STRING=$USER


# The scheduling priority for daemon processes.  See 'man nice'.
# export HBASE_NICENESS=10


# The directory where pid files are stored. /tmp by default.
export HBASE_PID_DIR=/home/hadoop/hbase-0.98.3-hadoop2


# Seconds to sleep between slave commands.  Unset by default.  This
# can be useful in large clusters, where, e.g., slave rsyncs can
# otherwise arrive faster than the master can service them.
# export HBASE_SLAVE_SLEEP=0.1


# Tell HBase whether it should manage it's own instance of Zookeeper or not.
export HBASE_MANAGES_ZK=false


# The default log rolling policy is RFA, where the log file is rolled as per the size defined for the 
# RFA appender. Please refer to the log4j.properties file to see more details on this appender.
# In case one needs to do log rolling on a date change, one should set the environment property
# HBASE_ROOT_LOGGER to "<DESIRED_LOG LEVEL>,DRFA".
# For example:
# HBASE_ROOT_LOGGER=INFO,DRFA
# The reason for changing default to RFA is to avoid the boundary case of filling out disk space as 
# DRFA doesn't put any cap on the log size. Please refer to HBase-5655 for more context.

<configuration>
    <property>
	    <name>hbase.rootdir</name>
	    <value>hdfs://mycluster/hbase</value> <span style="background-color: rgb(255, 0, 0);"> <!--必須和core-site.xml的fs.defaultFS值一致--></span>
	</property>
	<property>
	    <name>hbase.cluster.distributed</name>
	    <value>true</value>
	</property>
    <property>  
        <name>hbase.tmp.dir</name>  
        <value>/home/hadoop/hbase-0.98.3-hadoop2/tmp</value>  
    </property> 
    <property>
	    <name>hbase.zookeeper.quorum</name> 
	    <value>zk25,zk28,zk224</value>
	</property>
</configuration>

<pre name="code" class="html">hadoop25
hadoop28
hadoop201
hadoop224

（5）把hadoop/etc/hadoop/hdfs-site.xml檔案複製到hbase的conf目錄下

（這個很重要哦，否則會報錯誤，我就遇到問題了，報mycluster未未知的主機）

------------------------------------------------------------------------------------------------------------------------------------------------

===將上述動作在每一臺需要安裝hbase的節點上重複執行，呵呵，其實配好一臺機器，直接COPY更好====

------------------------------------------------------------------------------------------------------------------------------------------------

/home/hadoop/hbase-0.98.3-hadoop2/bin/start-hbase.sh

完成啟動了。

（7）看看hbase有否啟動成功？

http://hmaster:60010（你在那臺機器執行start-hbase.sh那麼哪一臺機器就是hmaster）

當然最直接了當的辦法還是看下日誌有沒有錯誤：

hbase-hadoop-regionserver-hadoop25log

hbase-hadoop-master-hadoop25.log