It seems that uninstalling zookeeper and re-installing it then gave me the
option to "Update Client Configurations" that seems to push out the zoo.cfg
to all the Flume hosts properly.

Once I did this, Flume finds my Hbase.

On Sat, Nov 17, 2012 at 12:57 AM, Patrick Ethier wrote:

I have a Flume service installed on 3 different hosts (meaning it uses the
same configuration settings). So, service flume1 has 3 instances.

The first instance, which is installed on the same system as the zookeeper
service, connects to my Hbase instance as expected.

The other two instances on the other hosts keeps on trying to connect to instead of connecting to the zookeeper instance.

The reason I suspect zookeeper is the following from the log output of the
other two agents:
12:54:17.293 AM INFO org.apache.zookeeper.ClientCnxn

Opening socket connection to server localhost/ Will not attempt to authenticate using SASL (Unable to locate a login configuration)

12:54:17.294 AM WARN org.apache.zookeeper.ClientCnxn

Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567)

at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:286)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1047)

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 4 | next ›
Discussion Overview
groupscm-users @
postedNov 20, '12 at 3:43p
activeNov 20, '12 at 4:47p



site design / logo © 2022 Grokbase