[
https://issues.apache.org/jira/browse/KAFKA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004157#comment-16004157
]
ASF GitHub Bot commented on KAFKA-5196:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/3008
KAFKA-5196: Make LogCleaner transaction-aware
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-5196
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3008.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #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)
