You know what, it's likely this is all because I'm running a bad fork of
Kafka 0.7.2 for Scala 2.10 (on the producers/consumers) since that's the
version we've standardized on.
Behavior in 2.9.2 with the official Kafka 0.7.2 release seems much more
normal -- I'm working on downgrading all our clie
As an update, this continues to affect us.
First I'd like to note ways in which my issues seems different than
KAFKA-278,
* I did not add a new broker or a new topic, this topic has been in use on
two existing brokers for months
* The topic definitely exists on both brokers. The topic/data direct
You are probably hitting https://issues.apache.org/jira/browse/KAFKA-278.
Can you please try the workaround mentioned in the JIRA description?
Thanks,
Neha
On Tue, Jun 4, 2013 at 4:21 PM, Brett Hoerner wrote:
> (version 0.7.2)
>
> For some reason, my producers are only picking up the partition
(version 0.7.2)
For some reason, my producers are only picking up the partition on 1 of my
2 brokers. I've been digging through the code, and I don't see any issues
given the state of my ZK nodes. The producer never seems to locate a
partition on Broker0, even though ZK clearly states that it has
