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 2021/07/28 18:28:00 UTC

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

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

Jason Gustafson resolved KAFKA-13099.
-------------------------------------
    Fix Version/s: 2.8.1
                   2.7.2
                   3.0.0
       Resolution: Fixed

> Message too large error when expiring transactionalIds
> ------------------------------------------------------
>
>                 Key: KAFKA-13099
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13099
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>             Fix For: 3.0.0, 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)