kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4776) Implement graceful handling for improperly formed compressed message sets
Date Mon, 20 Feb 2017 05:17:44 GMT

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

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

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/2572


> Implement graceful handling for improperly formed compressed message sets
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-4776
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4776
>             Project: Kafka
>          Issue Type: Bug
>          Components: log
>    Affects Versions: 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1, 0.10.2.0
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Minor
>             Fix For: 0.10.3.0
>
>
> This affects validation of compressed message sets. It is possible for a buggy client
to send both a null compressed message set (i.e. a wrapper message with a null value), and
an empty compressed message set (i.e. a wrapper message with valid compressed data in the
value field, but no actual records). In both cases, this causes an unexpected exception raised
from the deep iteration, which is returned to the client as an UNKNOWN_ERROR. It would be
better to return a CORRUPT_MESSAGE error.
> Note also that the behavior of the empty case was potentially more problematic in versions
prior to 0.10.2.0. Although we properly handled the null case, the broker would accept the
empty message set and write it to the log. The impact of this appears to be minor, but may
cause unexpected behavior in cases where we assume compressed message sets would contain some
records.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message