Open cangchen8180 opened 7 years ago
You should:
What I suspect: with Kafka <=0.10.0 (Logstash input plugin <=5.x), as soon as Logstash gets overwhelmed, Kafka thinks the consumer is dead are reallocates partitions to another node which in turn gets saturated.
I see this issue is still open, we are seeing something similar.
Logstash 5.4.1 and logstash-input-kafka-6.3.2
Our Logstash just freezes, nothing in the logs to indicate the problem and Kafka side it seems like the consumer have just disappeared. Restarting Logstash and we are away again for a random amount of time.
logstash 5.2.0
kafka 0.10.1
i found logstash consumer the kafka topic, when i want to use kafka-consumer-groups.sh to check the consumer suitation at kafka server , but kafka-consumer-groups.sh didn't found the consumer group info at the zookeeper .
Did this different than before? I am sure when used logstash 2.4.0 , it can be found consumer group at the zookeeper.
hi guy, now i have a knotty problem.
logstash cann't consume kafka message continuously.like this
sometimes be worse, like this
I not find out abnormal figure after trace gc times and heap size. And no error message in logstash.log.
message flow
version
I have
three logstash
, and one topic have20 partitions
. so i configconsumer_threads
is7
.logstash config
So please give me some tip !