The solution to the problem of HBase stand-alone mode configuration and inability to create tables
In this issue, the editor will bring you solutions to the problem of HBase stand-alone mode configuration and inability to create tables. The article is rich in content and analyzes and describes for you from a professional point of view. I hope you can get something after reading this article.
A few days ago, I wanted to try hbase. I just installed the click version, but I made a mistake when I created the table. I did something else for a while. I would like to recall the previous hbase when I am free today.
The click version of hbase I installed is 0.92.1. After downloading and decompressing it directly, it is added to the hbase-env file.
Export HBASE_OPTS= "- XX:+UseConcMarkSweepGC"
Export JAVA_HOME=/usr/local/java/jdk1.6.0_38/
Export HBASE_MANAGES_ZK=true
In hbase-site
Hbase.rootdir file:///home/bigfish/myhbase1/ hbase.zookeeper.property.dataDir / home/bigfish/myhbase1/zookeeper
Then start hbase Hmaseter and start hbsae shell.
You can use the list command or the status command, but there was a mistake in creating the table.
View the log under the log file:
2014-08-28 10 WARN org.apache.hadoop.hbase.master.AssignmentManager 2806791 WARN org.apache.hadoop.hbase.master.AssignmentManager: Unable to find a viable location to assign region-ROOT-,0.70236052
Org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed setting up proxy interface org.apache.hadoop.hbase.ipc.HRegionInterface to localhost/127.0.0.1:43673 after attempts=1
At org.apache.hadoop.hbase.ipc.HBaseRPC.waitForProxy (HBaseRPC.java:242)
At org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getHRegionConnection (HConnectionManager.java:1278)
At org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getHRegionConnection (HConnectionManager.java:1235)
At org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getHRegionConnection (HConnectionManager.java:1222)
At org.apache.hadoop.hbase.master.ServerManager.getServerConnection (ServerManager.java:496)
At org.apache.hadoop.hbase.master.ServerManager.sendRegionOpen (ServerManager.java:429)
At org.apache.hadoop.hbase.master.AssignmentManager.assign (AssignmentManager.java:1592)
At org.apache.hadoop.hbase.master.AssignmentManager.assign (AssignmentManager.java:1329)
At org.apache.hadoop.hbase.master.AssignCallable.call (AssignCallable.java:44)
At java.util.concurrent.FutureTask$Sync.innerRun (FutureTask.java:303)
At java.util.concurrent.FutureTask.run (FutureTask.java:138)
At java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:886)
At java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:908)
At java.lang.Thread.run (Thread.java:662)
Caused by: java.net.ConnectException: Connection refused
It is said that the ip address is not mapped correctly. Gedit / etc/hosts check and find out
Localhost 127.0.0.1
Bigfish 127.0.1.1
The two are not the same, both are changed to 127.0.0.1 and then restart hbase and then you can create tables.
The above is the solution to the HBase stand-alone mode configuration and the inability to create tables. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.
