Shulou(Shulou.com)06/01 Report--

When Hbase is installed today, in order to share ZK with kafka and other things, Hbase is not used and comes with ZK. As a result, a pit occurs. After the Hbase configuration is completed, it will not work. The log is as follows:

Java HotSpot (TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0Java HotSpot (TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m Support was removed in 8.0SLF4J: Class path contains multiple SLF4J bindings.SLF4J: Found binding in [jar:file:/Users/huzhixin/Cloud/hbase/lib/slf4j-log4j12-1.7.5.jarbank http://www.slf4j. SLF4J] SLF4J: Found binding in [jar:file:/Users/huzhixin/Cloud/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jarbank http://www.slf4j.] SLF4J: Org/codes.html#multiple_bindings for an explanation.SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. Shell) will not be able to find this ZK quorum.

Since I have just come into contact with this aspect, and the ZK is also set to 2181, I thought that the ZK port was set up related to Hbaseyou, and found that there was no

So all kinds of searches on the Internet, http://blog.chinaunix.net/uid-26275986-id-3824526.html from this article inspired to check port 2181, found that it is a java process, just like the author, so kill the process, and then Hbase starts successfully.

Disclaimer: it is purely a personal trampling record, which can only be guaranteed to be valid for my own problems.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.