Kafka still aware of old zookeeper nodes

2015-04-30 Thread Dillian Murphey
I had 3 zookeeper nodes. I added 3 new ones and shut down the old 3.

The server.log shows Closing socket connection error to the old IPs. I
rebooted the kafka server entirely but it still somehow seems aware of
these servers.

Any ideas what's up?


Re: Kafka still aware of old zookeeper nodes

2015-04-30 Thread svante karlsson
Have you changed

zookeeper.connect=

in server.properties.

A better procedure for replacing zookeeper nodes would be to shutdown one
and install the new one with the same ip. This can easily be done to a
running cluster.

/svante

2015-04-30 20:08 GMT+02:00 Dillian Murphey crackshotm...@gmail.com:

 I had 3 zookeeper nodes. I added 3 new ones and shut down the old 3.

 The server.log shows Closing socket connection error to the old IPs. I
 rebooted the kafka server entirely but it still somehow seems aware of
 these servers.

 Any ideas what's up?



Re: Kafka still aware of old zookeeper nodes

2015-04-30 Thread Dillian Murphey
Not sure if this is the best way to do this, but my zookeeper.connect is
set to a DNS alias which points to a load balancer for 3 zookeeper nodes.

I was trying this to see if I could have the kafka config dynamic and allow
me to change/scale whatever I wanted with zookeeper and not have to ever
mess with the config for kafka.

Thanks for your comments.

On Thu, Apr 30, 2015 at 11:35 AM, svante karlsson s...@csi.se wrote:

 Have you changed

 zookeeper.connect=

 in server.properties.

 A better procedure for replacing zookeeper nodes would be to shutdown one
 and install the new one with the same ip. This can easily be done to a
 running cluster.

 /svante

 2015-04-30 20:08 GMT+02:00 Dillian Murphey crackshotm...@gmail.com:

  I had 3 zookeeper nodes. I added 3 new ones and shut down the old 3.
 
  The server.log shows Closing socket connection error to the old IPs. I
  rebooted the kafka server entirely but it still somehow seems aware of
  these servers.
 
  Any ideas what's up?