You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/02/13 19:59:00 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17036473#comment-17036473 ] 

ASF GitHub Bot commented on KAFKA-9206:
---------------------------------------

agam commented on pull request #8111: KAFKA-9206: log a warning when encountering CORRUPT_MESSAGE
URL: https://github.com/apache/kafka/pull/8111
 
 
   - If the completed fetch has an error code signifying a _corrupt message_, log a specific warning for this (instead of the generic `Unexpected error code` right now).
   - Also added a test that triggers the warning and verifies it is logged.
   
   - Jira: https://issues.apache.org/jira/browse/KAFKA-9206
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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
>
> 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)