One of the be brokers (3) is not registered in ZK. Do you see ZK session expiration (potentially due to GC) in that broker?
Thanks, Jun On Mon, Feb 10, 2014 at 7:28 AM, Tomas Nunez <nu...@pythian.com> wrote: > Hi > > I'm new around here and I'm dealing with a problem, and reading the > documentation I don't know where else to look. > > I have a cross-dc mirrormaker setup: Mirrormaker is consuming from 5 > frontend servers in each DC (10 in total) and 5 backend servers are > consuming from mirrormaker. That's working for most of the topics, but some > of them are not being consumed from all backend servers. > > as an example, browsing with zkcli I find this: > > kafka-0.7.2-incubating-src/bin$ /usr/share/zookeeper/bin/zkCli.sh -server > zookeeperbe01:2181 ls /brokers/topics/topic1 > Connecting to zookeeperbe01:2181 > > WATCHER:: > > WatchedEvent state:SyncConnected type:None path:null > [2, 1, 5, 4] > kafka-0.7.2-incubating-src/bin$ /usr/share/zookeeper/bin/zkCli.sh -server > zookeeperfe01:2181 ls /brokers/topics/topic1 > Connecting to zookeeperfe01:2181 > > WATCHER:: > > WatchedEvent state:SyncConnected type:None path:null > [3, 2, 1, 5, 4] > > What can be wrong? Where can I look to get more info to troubleshoot this? > Any hint? > > Kafka version is 0.7.2, in mirromaker config I have "--num.streams 5 > --num.producers 5". Zookeeper version is 3.3.5, > > Here you can see kafka-console-consumer.sh connecting to both fe and be > servers: > https://gist.github.com/pythiannunez/1623934cb538678f053e > > Thanks! > > -- > > > -- > > > >
