Hi,
Best to keep the discussion in the JIRA. I asked a few questions.
Ismael
On Sat, Jan 5, 2019 at 9:38 AM Asaf Mesika wrote:
> Hi,
>
> We've recently started encountering the following exceptions, which appears
> to happen a lot on the Consumer side - we're using the old consumer (ZK
> based
Is there an existing Kafka Connect etcd source? Where the etcd keys on watch
update a Kafka topic. I thought I would ask before writing one. It's a
difficult Google search, because of all the interest in using etcd instead of
zookeeper in Kafka.
Hi,
We've recently started encountering the following exceptions, which appears
to happen a lot on the Consumer side - we're using the old consumer (ZK
based) and not the new (Camel based unfortunately).
*The exception*
kafka.common.KafkaException: Error processing data for partition
acmetopic-7
https://stackoverflow.com/questions/54039216/how-come-kafka-fails-to-commit-offset-for-a-particular-partition
https://stackoverflow.com/questions/54020753/why-is-kafka-producer-perf-test-sh-throwing-error
--
Thanks,
Ankur Rana
Software Developer
FarEye
Hello Margus,
Am not sure if I got your question correctly, but, assuming you have a
topic called "*kafka-log*" with two partitions, each of them (kafka-log-1
and kafka-log-2) will contain its own segments.
Kafka Brokers will distribute/replicate (according to the Brokers config)
the topics partit
Hey John,
Thanks for the response!
I will provide extra logs if it will happen again (I really really hope it
won't hehe :))
Some clarification regarding the previous mail:
The only thing that shows the data loss is the messages from the compacted
topic which I consumed a couple of hours after th
EDIT: At the end of the controller.log logs the following line should be
added:
ERROR [Controller 100]: Error while electing or becoming controller on
broker 100 (kafka.controller.KafkaController)
java.util.NoSuchElementException: key not found: 0
On Sat, Jan 5, 2019 at 4:21 PM Soheil Pourbafrani
Hi, using Kafka 11.0.3 I set up a 2 node Kafka cluster on CentOS 7 with
broker id 100 and 101. There is no firewall enabled. Both nodes can ping
each other and establish the SSH connection successfully.
When I start the cluster both broker successfully register their id into
the zookeeper cluster (