kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-1154) replicas may not have consistent data after becoming follower
Date Mon, 02 Dec 2013 21:58:35 GMT

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

Jun Rao resolved KAFKA-1154.
----------------------------

    Resolution: Fixed

Thanks for the review. Committed to trunk after addressing the minor review comments.

> replicas may not have consistent data after becoming follower
> -------------------------------------------------------------
>
>                 Key: KAFKA-1154
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1154
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8.1
>            Reporter: Jun Rao
>            Assignee: Jun Rao
>             Fix For: 0.8.1
>
>         Attachments: KAFKA-1154.patch
>
>
> This is an issued introduced in KAFKA-1001. The issue is that in ReplicaManager.makeFollowers(),
we truncate the log before marking the replica as the follower. New messages from the producer
can still be added to the log after the log is truncated, but before the replica is marked
as the follower. Those newly produced messages can actually be committed, which implies those
truncated messages are also committed. However, the new leader is not guaranteed to have those
truncated messages.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message