This may be due to https://issues.apache.org/jira/browse/KAFKA-1367
On Thu, Oct 03, 2013 at 04:17:45PM -0400, Florian Weingarten wrote:
> Hi list,
>
> I am trying to debug a strange issue we are seeing. We are using
> "Sarama" [1], our own Go implementation of the Kafka API.
>
> Somehow, we eith
I am seeing this behavior using librdkafka, as is another user.
Listing the topic metadata with the tool provided with Kafka
(kafka-topic.sh) shows all replicas in the ISR. However, using kafkacat[1]
(built with librdkafka) shows that many ISRs are missing some replicas. I
talked with Magnus (au
When you issue a metadata request to any broker, it responds with the
cluster metadata in memory. The broker gets it through an UpdateMetadata
request issued by the controller broker. If there are state changes in
flight, there may be a delay in the UpdateMetadata request propagation to
the broker
Hi list,
I am trying to debug a strange issue we are seeing. We are using
"Sarama" [1], our own Go implementation of the Kafka API.
Somehow, we either found a bug in Kafka, have a bug in our own code, or
got our cluster into a weird state. If we use our library to query Kafka
for metadata about a
