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 2022/03/17 23:13:00 UTC

[jira] [Updated] (KAFKA-13753) Log cleaner should retain transaction metadata in index until corresponding marker is removed

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

Jason Gustafson updated KAFKA-13753:
------------------------------------
    Summary: Log cleaner should retain transaction metadata in index until corresponding marker is removed  (was: Log cleaner should transaction metadata in index until corresponding marker is removed)

> Log cleaner should retain transaction metadata in index until corresponding marker is removed
> ---------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-13753
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13753
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> Currently the log cleaner will remove aborted transactions from the index as soon as it detects that the data from the transaction is gone. It does not wait until the corresponding marker has also been removed. Although it is extremely unlikely, it seems possible today that a Fetch might fail to return the aborted transaction metadata correctly if a log cleaning occurs concurrently. This is because the collection of aborted transactions is only done after the reading data from the log. It would be safer to preserve the aborted transaction metadata in the index until the marker is also removed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)