Comments (11)
@cdenneen looking at apache/kafka#6582 seems to be the client side, so upgrading should fix it. That said I'm no kafka expert, I've just been scouring exception messages and hunting open/closed issues :D
from logstash-input-kafka.
I updated the Logstash plugins today, and I no longer see the INVALID_FETCH_SESSION_EPOCH messages on the logs, so looking good to me. But, contrary to what someone mentioned above, I was still able to consume at high rate before the update, and from what I understand from KAFKA-8052 it would just cause retries.
from logstash-input-kafka.
@voiprodrigo You are right.
I was misunderstood. Actually messages was consumed despite the session log.
from logstash-input-kafka.
Even trying this:
max_poll_records => "200"
max_poll_interval_ms => "600000"
Still getting:
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872255710,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-1, groupId=devgilogs] Node 3 was unable to process the fetch request with (sessionId=1045052879, epoch=6): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872255845,"thread":"Ruby-0-Thread-65: :1","logEvent":{"message":"[Consumer clientId=rndlogstash1-0, groupId=devgilogs] Node 1 was unable to process the fetch request with (sessionId=1934164936, epoch=7): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872265350,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 3 was unable to process the fetch request with (sessionId=508411314, epoch=37): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872277017,"thread":"Ruby-0-Thread-67: :1","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 1 was unable to process the fetch request with (sessionId=808909764, epoch=27): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872277017,"thread":"Ruby-0-Thread-67: :1","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 3 was unable to process the fetch request with (sessionId=444142735, epoch=11): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872325905,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 2 was unable to process the fetch request with (sessionId=1200630398, epoch=33): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872347272,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 2 was unable to process the fetch request with (sessionId=301078840, epoch=9): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872371926,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 3 was unable to process the fetch request with (sessionId=1710138438, epoch=68): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872372792,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-2, groupId=devgilogs] Node 2 was unable to process the fetch request with (sessionId=1464246895, epoch=12): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872383628,"thread":"Ruby-0-Thread-65: :1","logEvent":{"message":"[Consumer clientId=rndlogstash1-0, groupId=devgilogs] Node 2 was unable to process the fetch request with (sessionId=122035194, epoch=120): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872398868,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-0, groupId=devgilogs] Node 1 was unable to process the fetch request with (sessionId=127336610, epoch=62): INVALID_FETCH_SESSION_EPOCH."}}
{"level":"INFO","loggerName":"org.apache.kafka.clients.FetchSessionHandler","timeMillis":1562872398874,"thread":"kafka-coordinator-heartbeat-thread | devgilogs","logEvent":{"message":"[Consumer clientId=rndlogstash1-0, groupId=devgilogs] Node 2 was unable to process the fetch request with (sessionId=229221809, epoch=17): INVALID_FETCH_SESSION_EPOCH."}}
from logstash-input-kafka.
I also encountered the same situation.
Logstash can not consume message from kafka at all.
No workaround exists?
from logstash-input-kafka.
This seems related to this kafka bug https://issues.apache.org/jira/browse/KAFKA-8052
I created #327 to upgrade the client to 2.3.0, we'll publish it soon.
from logstash-input-kafka.
input and output kafka plugins have been released with kafka client 2.3.0:
https://github.com/logstash-plugins/logstash-input-kafka/blob/master/CHANGELOG.md#910
https://github.com/logstash-plugins/logstash-output-kafka/blob/master/CHANGELOG.md#810
from logstash-input-kafka.
@jsvd is this a client side bug only or server side? I'm guessing it's client side so upgrading logstash to use the 2.3.0 plugin with 2.1.0 server should fix the issue?
from logstash-input-kafka.
I am getting the same errror.
2019-08-22 14:15:03.458 INFO 3193 --- [pool-1-thread-1] o.a.k.c.FetchSessionHandler : [Consumer clientId=consumer-1, groupId=aaaa2] Error sending fetch request (sessionId=INVALID, epoch=INITIAL) to node 3: org.apache.kafka.common.errors.DisconnectException.
2019-08-22 14:15:33.659 INFO 3193 --- [pool-1-thread-1] o.a.k.c.FetchSessionHandler : [Consumer clientId=consumer-1, groupId=aaaa2] Error sending fetch request (sessionId=INVALID, epoch=INITIAL) to node 1: org.apache.kafka.common.errors.DisconnectException.
upgraded to latest version of kafka still not working , i am not even able to establish a initial connection also
from logstash-input-kafka.
Seeing this. What was the solution?
from logstash-input-kafka.
@ashishbhumireddy , did you solve this issue? I've got the same one.
from logstash-input-kafka.
Related Issues (20)
- decorate_events is missing to catch message size
- SASL JAAS - Could not find a 'KafkaClient' entry in the JAAS configuration HOT 2
- logstash6.6 with Kafka Client Version 0.8 input HOT 2
- don't join group until pipeline is initialized to prevent premature rebalancing HOT 1
- Multiple Kafka inputs - 7.x HOT 3
- logstash-6.3.2 can not connect kafka 0.10.2,Please help HOT 2
- Bump to Kafka client 2.3.0
- [Doc] Kafka input ACL permissions HOT 1
- logstash doesn't renew kafka ip when kafka pod restarts HOT 1
- kafka meta data timestamp issue. HOT 2
- Bump to Kafka client to 2.4.0 HOT 2
- Add feature to attach record headers to events HOT 2
- the `record.value.to_s` method prevent codec plain charset settings HOT 2
- Kafka input plug-in skip reading from single partition from assigned topic
- Confluent Avro - schema_registry : https and basic auth do not work HOT 1
- topics_pattern limits parallel consumption of matching topics' partitions HOT 2
- Please add an option for group.instance.id support
- Kafka auto-commit on failed index events
- Tombstones are swallowed in an Avro topic: please give them to the pipeline, with [@metadata][kafka][tombstone]=true
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from logstash-input-kafka.