You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2019/09/10 05:28:00 UTC

[jira] [Resolved] (KAFKA-8889) Root cause is lost for FetchSessionHandler.handleError

     [ https://issues.apache.org/jira/browse/KAFKA-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guozhang Wang resolved KAFKA-8889.
----------------------------------
    Resolution: Fixed

> Root cause is lost for FetchSessionHandler.handleError
> ------------------------------------------------------
>
>                 Key: KAFKA-8889
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8889
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Qinghui Xu
>            Priority: Minor
>
> FetchSessionHandler is not logging properly the errors, and produces error messages sometimes hard to understand the root cause.
> More precisely, FetchSessionHandler.handleError prints Throwable.toString, which is merely a summary message, and loses the stacktrace of the error. For example, we can get some messages, but cannot get a clue about why:
> {code:java}
> Error sending fetch request (sessionId=1655236778, epoch=99) to node 01: org.apache.kafka.common.errors.DisconnectException {code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)