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 2017/05/12 19:33:04 UTC
[jira] [Resolved] (KAFKA-5196) LogCleaner should be
transaction-aware
[ https://issues.apache.org/jira/browse/KAFKA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-5196.
------------------------------------
Resolution: Fixed
Issue resolved by pull request 3008
[https://github.com/apache/kafka/pull/3008]
> LogCleaner should be transaction-aware
> --------------------------------------
>
> Key: KAFKA-5196
> URL: https://issues.apache.org/jira/browse/KAFKA-5196
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, core, producer
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Critical
> Fix For: 0.11.0.0
>
>
> In accordance with the KIP-98 design, the log cleaner should be aware of transaction markers. This means the following:
> 1. Cleaning should be restricted below the last stable offset (which ensures that only decided data is considered when cleaning).
> 2. Records from aborted transactions are removed immediately.
> 3. Removal of the COMMIT/ABORT markers must be delayed to ensure that they are not missed by concurrent readers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)