[jira] [Updated] (KAFKA-13099) Message too large error when expiring transactionalIds

["Jason Gustafson (Jira)" <ji...@apache.org>]

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

Jason Gustafson updated KAFKA-13099:
------------------------------------
    Fix Version/s: 2.6.3
                   2.5.2

> Message too large error when expiring transactionalIds
> ------------------------------------------------------
>
>                 Key: KAFKA-13099
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13099
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.0.1, 2.1.1, 2.2.2, 2.3.1, 2.4.1, 2.5.1, 2.6.1, 2.8.0, 2.7.1
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>             Fix For: 3.0.0, 2.5.2, 2.6.3, 2.7.2, 2.8.1
>
>
> We have seen a couple reports of MESSAGE_TOO_LARGE errors when writing tombstones for expired transactionalIds. This is possible because we collect all expired IDs into a single batch. We should ensure that the created batches are smaller than the max message size. Any expired IDs that cannot fit can be expired later.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)