kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sunilkalva (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2292) failed fetch request logging doesn't indicate source of request
Date Wed, 12 Oct 2016 20:42:20 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569819#comment-15569819
] 

sunilkalva commented on KAFKA-2292:
-----------------------------------

[~malaskat] Any updates ?

> failed fetch request logging doesn't indicate source of request
> ---------------------------------------------------------------
>
>                 Key: KAFKA-2292
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2292
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Rosenberg
>            Assignee: Ted Malaska
>
> I am trying to figure out the source of a consumer client that is issuing out of range
offset requests for a topic, on one for our brokers (we are running 0.8.2.1).
> I see log lines like this:
> {code}
> 2015-06-20 06:17:24,718 ERROR [kafka-request-handler-4] server.ReplicaManager - [Replica
Manager on Broker 123]: Error when processing fetch request for partition [mytopic,0] offset
82754176 from consumer with correlation id 596. Possible cause: Request for offset 82754176
but we only have log segments in the range 82814171 to 83259786.
> {code}
> Successive log lines are similar, but with the correlation id incremented, etc.
> Unfortunately, the correlation id is not particularly useful here in the logging, because
I have nothing to trace it back to to understand which connected consumer is issuing this
request.  It would be useful if the logging included an ip address, or a clientId.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message