You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/02/21 18:04:00 UTC
[jira] [Resolved] (KAFKA-9206) Consumer should handle
`CORRUPT_MESSAGE` error code in fetch response
[ https://issues.apache.org/jira/browse/KAFKA-9206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-9206.
------------------------------------
Fix Version/s: 2.6.0
Resolution: Fixed
> Consumer should handle `CORRUPT_MESSAGE` error code in fetch response
> ---------------------------------------------------------------------
>
> Key: KAFKA-9206
> URL: https://issues.apache.org/jira/browse/KAFKA-9206
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Agam Brahma
> Priority: Major
> Fix For: 2.6.0
>
>
> This error code is possible, for example, when the broker scans the log to find the fetch offset after the index lookup. Currently this results in a slightly obscure message such as the following:
> {code:java}
> java.lang.IllegalStateException: Unexpected error code 2 while fetching data{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)