You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2019/06/21 16:47:00 UTC

[jira] [Resolved] (KAFKA-8570) Downconversion could fail when log contains out of order message formats

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

Jason Gustafson resolved KAFKA-8570.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.2
                   2.1.2
                   2.0.2
                   2.3.1

> Downconversion could fail when log contains out of order message formats
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-8570
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8570
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Dhruvil Shah
>            Assignee: Dhruvil Shah
>            Priority: Major
>             Fix For: 2.3.1, 2.0.2, 2.1.2, 2.2.2
>
>
> When the log contains out of order message formats (for example a v2 message followed by a v1 message), it is possible for down-conversion to fail in certain scenarios where batches compressed and greater than 1kB in size. Down-conversion fails with a stack like the following:
> java.lang.IllegalArgumentException
> at java.nio.Buffer.limit(Buffer.java:275)
> at org.apache.kafka.common.record.FileLogInputStream$FileChannelRecordBatch.writeTo(FileLogInputStream.java:176)
> at org.apache.kafka.common.record.AbstractRecords.downConvert(AbstractRecords.java:107)
> at org.apache.kafka.common.record.FileRecords.downConvert(FileRecords.java:242)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)