You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2016/12/15 19:29:58 UTC

[jira] [Updated] (KAFKA-4546) a consumer could miss tombstone when leader changes during the reads

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

Jun Rao updated KAFKA-4546:
---------------------------
    Affects Version/s: 0.10.1.0

This is affecting all versions of Kafka. Not sure what's the best way to address this though. If anyone has an idea, please chime in.

> a consumer could miss tombstone when leader changes during the reads
> --------------------------------------------------------------------
>
>                 Key: KAFKA-4546
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4546
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.2.1, 0.10.1.0
>            Reporter: Jun Rao
>
> Currently, in a compacted topic, we delay the removal of a tombstone by delete.retention.ms to avoid the case that a consumer reads a non-tombstone before the tombstone, then tombstone is removed and the consumer misses the tombstone.
> However, tombstones are removed independently in different replicas. Supposed that a tombstone is already removed in the follower, but not in the leader. A consumer could read a non-tombstone message on the leader, then the leader changes, and the consumer will miss the tombstone on the new leader since it's already deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)