suseendramani created KAFKA-8327:
------------------------------------
Summary: Connection to Node2 was disconnected
Key: KAFKA-8327
URL: https://issues.apache.org/jira/browse/KAFKA-8327
Project: Kafka
Issue Type: New Feature
Components: consumer
Affects Versions: 1.1.0
Reporter: suseendramani
Hi Team,
we are seeing the below errors in the kafka logs. We are using the kafka
version 1.1.0, COuld you please let us know if there are any fixes that can
be applied to this ?
[2019-05-06 20:40:23,212] INFO [ReplicaFetcher replicaId=3, leaderId=2,
fetcherId=0] Error sending fetch request (sessionId=896515694, epoch=738904) to
node 2: java.io.IOException: Connection to 2 was disconnected before the
response wa
s read. (org.apache.kafka.clients.FetchSessionHandler)
[2019-05-06 20:40:23,422] WARN [ReplicaFetcher replicaId=3, leaderId=2,
fetcherId=0] Error in response for fetch request (type=FetchRequest,
replicaId=3, maxWait=500, minBytes=1, maxBytes=10485760,
fetchData=\{xxx-12=(offset=38826573, logStartOffset=38549032,
maxBytes=1048576), xxxxxx-14=(offset=49033, logStartOffset=0,
maxBytes=1048576), rWithSubscription-Cas-3=(offset=40752457,
logStartOffset=40198369, maxBytes=1048576), xxxxxx-8=(offset=39543295,
logStartOffset=39032103, maxBytes=1048576)}, isolationLevel=READ_UNCOMMITTED,
toForget=, metadata=(s
essionId=896515694, epoch=738904)) (kafka.server.ReplicaFetcherThread)
java.io.IOException: Connection to 2 was disconnected before the response was
read
We are also seeing the below errors..
[2019-05-07 01:39:57,310] INFO [ReplicaFetcher replicaId=0, leaderId=4,
fetcherId=0] Retrying leaderEpoch request for partition __consumer_offsets-31
as the leader reported an error: NOT_LEADER_FOR_PARTITION
(kafka.server.ReplicaFetcherThread)
Please let us know the reason for the same.
Thanks,
Mani
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
