On Tue, Oct 18, 2011 at 15:02, Mathias Herberts
<[email protected]> wrote:
>> I think Jun or Neha had tracked this one down at LinkedIn and it is actually
>> a zk bug. I think it is this one, but they could confirm:
>>
>> https://issues.apache.org/jira/browse/ZOOKEEPER-961
>
> Sure looks like it.
Confirmed. Running the above repro against zookeeper trunk produces a
responsive consumer that successfully rebalances when the broker
rejoins.
> So besides waiting for ZK 3.3.4 there is not much that can be done
> since Kafka does not offer a way to change the root znode of a
> cluster.
Yeah, it's unclear that zk-3.3.4 will release anytime soon. Instead of
relying on zk chroot, why not just expose the zk paths as config
parameters for consumers, brokers, and producers?
object ZkUtils {
val ConsumersPath = "/consumers"
val BrokerIdsPath = "/brokers/ids"
val BrokerTopicsPath = "/brokers/topics"
...
