Hbase有内置的zookeeper，上一篇文章我就是使用Hbase内置的zookeeper启动Hbase的，如果想要使用外部独立的Zookeeper，需要将conf/hbase-env.sh中的HBASE_MANAGES_ZK设置为false，使内置的Zookeeper不受Hbase管理，不随Hbase启动而启动，不随Hbase停止而停止

 ​# Tell HBase whether it should manage its own instance of ZooKeeper or not.
 ​export HBASE_MANAGES_ZK=false

当你想使用Hbase内置的Zookeeper，又不想因为停止或启动Hbase时，Zookeeper跟着停止或启动，可以执行以下命令
${HBASE_HOME}/bin/hbase-daemons.sh {start,stop} zookeeper

官网 https://zookeeper.apache.org/

选择要下载的版本

点击下载

上传到服务器你指定的目录并解压

需要将conf文件夹中的zoo_sample.cfg文件复制并将文件名改为 zoo.cfg

打开zoo.cfg文件，并在zoo.cfg文件末尾加上这两项配置

export ZOOKEEPER_HOME=/usr/local/zookeeper
export PATH=$PATH:$ZOOKEEPER_HOME/bin

进入zookeeper的bin目录，启动Zookeeper

./zkServer.sh start

修改Hbase的hbase-site.xml文件

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl" target="_blank" rel="external nofollow" ?>
<!--
/*
 * 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.
 */
-->
<configuration>
  <!--
    The following properties are set for running HBase as a single process on a
    developer workstation. With this configuration, HBase is running in
    "stand-alone" mode and without a distributed file system. In this mode, and
    without further configuration, HBase and ZooKeeper data are stored on the
    local filesystem, in a path under the value configured for `hbase.tmp.dir`.
    This value is overridden from its default value of `/tmp` because many
    systems clean `/tmp` on a regular basis. Instead, it points to a path within
    this HBase installation directory.

    Running against the `LocalFileSystem`, as opposed to a distributed
    filesystem, runs the risk of data integrity issues and data loss. Normally
    HBase will refuse to run in such an environment. Setting
    `hbase.unsafe.stream.capability.enforce` to `false` overrides this behavior,
    permitting operation. This configuration is for the developer workstation
    only and __should not be used in production!__

    See also https://hbase.apache.org/book.html#standalone_dist
  -->
  <property>
    <name>hbase.cluster.distributed</name>
    <value>false</value>
  </property>
  <property>
    <name>hbase.tmp.dir</name>
    <value>./tmp</value>
  </property>
  <property>
    <name>hbase.unsafe.stream.capability.enforce</name>
    <value>false</value>
  </property>
  <property>
    <name>hbase.rootdir</name>
    <value>file:///home/hbase</value>
  </property>
  <property>
    <name>hbase.zookeeper.quorum</name>
    <value>master</value>
  </property>
  <property>
    <name>hbase.zookeeper.property.clientPort</name>
    <value>2181</value>
  </property>

</configuration>

当我启动外部独立的Zookeeper，启动Hbase连接时，报错，显示Hbase依然使用内置的Zookeeper，并与我的外部Zookeeper端口冲突

查看Hbase的hbase-site.xml文件，因为把hbase.cluster.distributed设置为false, 也就是让hbase以standalone模式运行时,依然会去启动自带的zookeeper。

所以要做如下设置,值为true：

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

注：hbase.zookeeper.quorum中的master为我在/etc/hosts中配置的

再次启动Hbase，启动成功