我正在使用带有存储后端的titandb hbase manage by zookeeper和index backend:elasticsearch我的问题是hbase连接zookeeper并立即断开连接,但代码以0退出。
====================ElasticSearch.yml=====
cluster.name: elasticsearch_graph_dev
script.disable_dynamic: true
node.name: "node_graph_dev"
bootstrap.mlockall: true
network.host: 127.0.0.1
======================hbase-site.xml========
<configuration>
<property>
<name>hbase.zookeeper.property.dataDir</name>
<value>/zookeeper</value>
</property>
<property>
<name>zookeeper.znode.parent</name>
<value>/hbase-unsecure</value>
</property>
<property>
<name>hbase.manages.zk</name>
<value>true</value>
</property>
<property>
<name>hbase.cluster.distributed</name>
<value>true</value>
</property>
</configuration>
================动物园.cfg========
enter code here
tickTime=2000
initLimit=10
syncLimit=5
dataDir=/tmp/zookeeper
clientPort=2181
================控制台上的消息=====
[main] INFO org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=localhost:2181 sessionTimeout=90000 watcher=hconnection-0x2a097d77, quorum=localhost:2181, baseZNode=/hbase-unsecure
[main] INFO org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper - Process identifier=hconnection-0x2a097d77 connecting to ZooKeeper ensemble=localhost:2181
[main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
[main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Socket connection established to localhost/127.0.0.1:2181, initiating session
[main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Session establishment complete on server localhost/127.0.0.1:2181, sessionid = 0x154526f4c3e214d, negotiated timeout = 40000
[main] INFO org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=localhost:2181 sessionTimeout=90000 watcher=catalogtracker-on-hconnection-0x2a097d77, quorum=localhost:2181, baseZNode=/hbase-unsecure
[main] INFO org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper - Process identifier=catalogtracker-on-hconnection-0x2a097d77 connecting to ZooKeeper ensemble=localhost:2181
[main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error)
[main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Socket connection established to localhost/0:0:0:0:0:0:0:1:2181, initiating session
[main-SendThread(localhost:2181)] INFO org.apache.zookeeper.ClientCnxn - Session establishment complete on server localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x154526f4c3e214e, negotiated timeout = 40000
[main] INFO org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation - Closing zookeeper sessionid=0x154526f4c3e214d
[main] INFO org.apache.zookeeper.ZooKeeper - Session: 0x154526f4c3e214d closed
[main-EventThread] INFO org.apache.zookeeper.ClientCnxn - EventThread shut down
[main] INFO org.apache.zookeeper.ZooKeeper - Session: 0x154526f4c3e214e closed
[main-EventThread] INFO org.apache.zookeeper.ClientCnxn - EventThread shut down
[main] INFO org.apache.hadoop.hbase.client.HBaseAdmin - Started disable of titan
Titan version = 1.0.0
hbase version = 0.98.12
zookeeper version = 3.4.6
elasticsearch version = 1.5.1
======================================================
上面的消息一直在打印很多次,我只想知道它是否可以打印多次或只有一次(然后如何解决它)。
我可以看到我在elasticsearch gui中创建的索引,也可以看到hbase terminal+gui中的表。
谢谢
编辑
hbase日志:
2016-04-28 14:01:41,884 INFO [pool-14-thread-1] catalog.CatalogTracker: Failed verification of hbase:meta,,1 at address=172.20.56.111,60020,1461827886746, exception=java.net.ConnectException: Connection refused
2016-04-28 14:01:41,884 INFO [pool-14-thread-1] master.HMaster: Forcing expire of 172.20.56.111,60020,1461827886746
2016-04-28 14:01:41,885 INFO [pool-14-thread-1] master.ServerManager: Master doesn't enable ServerShutdownHandler during initialization, delay expiring server 172.20.56.111,60020,1461827886746
1条答案
按热度按时间h79rfbju1#
如前所述,这些都只是
INFO
信息。只是噪音。如果它们困扰您,您可以使用log4j属性来配置日志级别以减少它们。