Summary of problems in Hbase Configuration

The following problems occur during create table:

1. ERROR: java. io. IOException: Table Namespace Manager not ready yet, try again later

Solution: this problem occurs from single-host configuration to multi-host configuration, modify conf/hbase-env.sh comment out export HBASE_MANAGES_ZK = true

2. java.net. socketTimeoutException: Call to datanode1/172.16.0.122: 60020 failed because java.net. socketTimeoutException: 60000 millis timeout while waiting for channel to be ready for read. ch: java. nio. channels. socketChannel [connected local =/172.16.0.126: 55277 remote = datanode1/172.16.0.122: 60020]

Problem: The time configured for zookeeper. session. timeout in the master and slave hbase-site.xml is inconsistent

Solution: Configure zookeeper. session. timeout in the hbase-site.xml on the master server and slave server to 120000

3. RegionServer not running

View logs: 22:02:20, 112 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:21, 113 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:22, 114 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:23, 115 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:24, 118 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:25, 119 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:26, 121 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:27, 122 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:28, 123 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:29, 124 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:30, 126 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:31, 127 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:32, 129 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:33, 130 INFO [master: localhost: 60000] master. ServerManager: Waiting on regionserver (s) to go down localhost, 60020,1401974130087
22:02:33, 667 INFO [master: localhost: 60000. oldLogCleaner] cleaner. LogCleaner: master: localhost: 60000. oldLogCleaner exiting
22:02:33, 668 INFO [master: localhost: 60000. oldLogCleaner] master. ReplicationLogCleaner: Stopping replicationLogCleaner-0x466c2b7c4b0003, quorum = datanode1: 2222, robinson-ubuntu: 2222, baseZNode =/hbase
22:02:33, 684 INFO [master: localhost: 60000. archivedHFileCleaner] cleaner. HFileCleaner: master: localhost: 60000. archivedHFileCleaner exiting
22:02:33, 691 INFO [master: localhost: 60000. oldLogCleaner] zookeeper. ZooKeeper: Session: 0x466c2b7c4b0003 closed

Problem: in/etc/hosts, configure the host name to 127.0.0.1.

Solution: Set the host name to the actual IP address.