"Hadoop" HBase Distributed Link error problem, cannot be connected to other nodes to handle problems after startup. The error has been node/hbase the "not" in ZooKeeper. The problem cannot be synchronized.

The following error messages are executed

2016-12-09 19:38:17,672 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '.
There could is a mismatch with the one configured in the master. 2016-12-09 19:38:17,779 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '.
There could is a mismatch with the one configured in the master. 2016-12-09 19:38:17,981 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '.
There could is a mismatch with the one configured in the master. 2016-12-09 19:38:18,284 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It sHould has been written by the master. Check the value configured in ' Zookeeper.znode.parent '.
There could is a mismatch with the one configured in the master. 2016-12-09 19:38:18,786 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '.
There could is a mismatch with the one configured in the master. 2016-12-09 19:38:19,790 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '.
There could is a mismatch with the one configured in the master. 2016-12-09 19:38:21,797 ERROR [main] client. Connectionmanager$hconnectionimplementation:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '. There could is a mismatch with theOne configured in the master. Error:the Node/hbase is not in ZooKeeper. It should has been written by the master. Check the value configured in ' Zookeeper.znode.parent '. There could is a mismatch with the one configured in the master.

The following are the log messages:

2016-12-09 19:54:33,045 ERROR [main] master. Hmastercommandline:master exiting
java.io.IOException:Could not the start ZK at requested port of 2181.  ZK is started at port:2182.  Aborting as clients (e.g. shell) is not being able to find this ZK quorum.
    At Org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster (hmastercommandline.java:212) at
    Org.apache.hadoop.hbase.master.HMasterCommandLine.run (hmastercommandline.java:137) at
    Org.apache.hadoop.util.ToolRunner.run (toolrunner.java:70) at
    Org.apache.hadoop.hbase.util.ServerCommandLine.doMain (servercommandline.java:126) at
    Org.apache.hadoop.hbase.master.HMaster.main (hmaster.java:2436)
2016-12-09 19:54:33,058 INFO  [Thread-2] Server. nioservercnxn:closed Socket connection for CLIENT/127.0.0.1:3168 (no session established for client)

It is clear that the port 2181 is occupied, and because the search for a half-day do not know the port is occupied by which,
I personally suspect that it is not the Hadoop middleware series which opened the zookeeper this default port to occupy.
Not sure, so it's not good to kill this port, so you can only modify the default port:
Modify in hbase-site.xml
Make 2181 into 2182

<property>
     <name>hbase.zookeeper.property.clientPort</name>
     <value>2182</ Value>                                                                                                                                             

Post-execution results
Information display

[Root@master bin]#/start-hbase.sh 
starting master, logging To/home/hbase/logs/hbase-root-master-master.out
Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; support is removed in 8.0
Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Support is removed in 8.0
Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; Ed in 8.0
Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m;
Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; Support is removed in 8.0
Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Moved in 8.0
Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m;
Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Support is removed in 8.0

Log display

[root@master bin]#./start-hbase.sh starting master, logging to/home/hbase/logs/ Hbase-root-master-master.out Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option permsize=128m; Support is removed in 8.0 Java HotSpot (TM) 64-bit Server VM warning:ignoring option maxpermsize=128m; Support is removed in 8.0 

can see success.
At the same time we open the Web shell, see before entering the list when the hint of the link does not port 2181 is still there.

HBase (main):001:0> list
TABLE                                                                                                                               
0 Row (s) in 0.7930 seconds

= []

Smooth execution

In addition, during the entire process, the confusion about the configuration is also written down.
First
Even a master three slave
However, in the configuration quorum can only write the other three slave

<property>
        <name>base.zookeeper.quorum</name>
        <value>slave1,slave2,slave3</ Value>
</property>

Second, for the sake of insurance, or configure zookeeper yourself ... All that comes with is a pit (tears
Then you also need to modify the environment hbase-env.sh.

Export Hbase_manages_zk=false

Third, if there is an error saying to see if the zookeeper.znode.parent configuration is good,
It would be better for you to define it directly in XML to avoid any other mistakes.
At the same time to cooperate with Rootserver together.

<property> <name>zookeeper.znode.parent</name> <value>/hbase</value> <d Escription>root Znode for HBase in ZooKeeper.  
      All of HBase's ZooKeeper files that is configured with a relative path would go under this node.  By default, all of HBase ' s ZooKeeper file path is configured with a relative path, so they would all go under this  
    directory unless changed.  
    </description> </property> <property> <name>zookeeper.znode.rootserver</name> <value>root-region-server</value> <description>path to Znode holding root, location. This was written by the master and read by clients and region servers. If A relative path is given, the parent folder would be ${zookeeper.znode.parent}.  
    By default, this means the root is stored at/hbase/root-region-server.  </description> </property>

Four, you want to be not pseudo-distributed, be sure to specify

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