I think the way reassignment works is asynchronous. Changes are made to
zookeeper but those changes get reflected only when controller watcher
fires for the respective zookeeper path. Is your watcher still alive?
Thanks,
Mayuresh
On Tue, Mar 17, 2015 at 1:29 PM, Allen Wang
Hello,
I developed a tool to add partitions and assign new partitions to a set of
brokers in one operation by utilizing the API
AdminUtils.createOrUpdateTopicPartitionAssignmentPathInZK().
It worked well in most cases. However, in one case, I found that the
brokers are not aware of new
Yes, the watcher is still alive. The log in the controller indicates that
it observed the changes.
On Tue, Mar 17, 2015 at 2:05 PM, Mayuresh Gharat gharatmayures...@gmail.com
wrote:
I think the way reassignment works is asynchronous. Changes are made to
zookeeper but those changes get
Probably you can try restarting the controller and have same version for
the controller and the brokers.
BTW, was there any specific reason you are running 2 different versions for
the controller and other brokers?
Thanks,
Mayuresh
On Tue, Mar 17, 2015 at 4:02 PM, Allen Wang
I am not sure if Kafka version difference is the issue as later adding
partitions for other topics works. Is there any compatibility issues on
protocol level in 0.8.2.1 vs. 0.8.1.1?
Also restarting the controller seems to fix the problem.
On Tue, Mar 17, 2015 at 4:08 PM, Mayuresh Gharat
Looking a bit more into controller log, it seems that when the partition
assignment is changed in ZooKeeper, the controller has quite a lot
exceptions communicating with new brokers where the partitions are
assigned. One thing to note is that the new brokers have Kafka version
0.8.2.1 and the
