Yeah the issue was mostly that literally ALL of the docs use / as the
chroot. People kept getting tripped up with the ZK URL with /kafka, it's a
bit funky eg:
host1.domain.com:2181,host2.domain.com:2181,host3.domain.com:2181/kafka. So
we opted to change it back to what everyone else is doing by d
Yes, turns out that during the upgrade from CDH5.2 to CDH5.3, the namespace
changed from "/kafka" to simply "/" on Zk. I spoke with the developers over
at Cloudera and they said, using "/" seemed to be the convention. I am
going to open a case with them to clearly document the change so other
custo
Is the broker configured with the correct ZK url and the right namespace?
Thanks,
Jun
On Fri, Jan 23, 2015 at 12:17 AM, Tim Smith wrote:
> Using kafka 0.8.1.1, the cluster had been healthy with producers and
> consumers being able to function well. After a restart of the cluster, it
> looks li
