Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Wed, 18 Oct 2017 22:29:02 +0000 (UTC)
From: "Jun Rao (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12928676.1452268912000.2511.1508365742058@Atlassian.JIRA>
In-Reply-To: <JIRA.12928676.1452268912000@Atlassian.JIRA>
References: <JIRA.12928676.1452268912000@Atlassian.JIRA> <JIRA.12928676.1452268912155@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (KAFKA-3083) a soft failure in controller may
 leave a topic partition in an inconsistent state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 Oct 2017 22:29:08 -0000


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

Jun Rao resolved KAFKA-3083.
----------------------------
       Resolution: Fixed
         Assignee: Onur Karaman  (was: Mayuresh Gharat)
    Fix Version/s: 1.1.0

This is now fixed in KAFKA-5642.

> 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: Onur Karaman
>              Labels: reliability
>             Fix For: 1.1.0
>
>
> 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)