kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3083) a soft failure in controller may leave a topic partition in an inconsistent state
Date Thu, 07 Sep 2017 00:35:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156244#comment-16156244
] 

Guozhang Wang commented on KAFKA-3083:
--------------------------------------

[~dibbhatt] KAFKA-5027 is being actively worked on and expected to be released in the next
release (mid Oct.), which would resolve this issue.

> a soft failure in controller may leave a topic partition in an inconsistent state
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-3083
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3083
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.9.0.0
>            Reporter: Jun Rao
>            Assignee: Mayuresh Gharat
>              Labels: reliability
>
> The following sequence can happen.
> 1. Broker A is the controller and is in the middle of processing a broker change event.
As part of this process, let's say it's about to shrink the isr of a partition.
> 2. Then broker A's session expires and broker B takes over as the new controller. Broker
B sends the initial leaderAndIsr request to all brokers.
> 3. Broker A continues by shrinking the isr of the partition in ZK and sends the new leaderAndIsr
request to the broker (say C) that leads the partition. Broker C will reject this leaderAndIsr
since the request comes from a controller with an older epoch. Now we could be in a situation
that Broker C thinks the isr has all replicas, but the isr stored in ZK is different.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message