You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/11/30 15:41:58 UTC
[jira] [Updated] (KAFKA-4433) Kafka Controller Does not send a
LeaderAndIsr to old leader of a topicPartition during reassignment, if the
old leader is not a part of the new assigned replicas
[ https://issues.apache.org/jira/browse/KAFKA-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-4433:
-------------------------------
Labels: reliability (was: )
> Kafka Controller Does not send a LeaderAndIsr to old leader of a topicPartition during reassignment, if the old leader is not a part of the new assigned replicas
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4433
> URL: https://issues.apache.org/jira/browse/KAFKA-4433
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Reporter: Mayuresh Gharat
> Assignee: Mayuresh Gharat
> Labels: reliability
> Fix For: 0.10.2.0
>
>
> Consider the following scenario :
> old replicas : {[1,2,3], Leader = 1} is reassigned to new replicas : {[2,3,4], Leader = 2}
> In this case broker 1 does not receive a LeaderAndIsr request to become a follower.
> This happens because of the following :
> val (leaderAndIsr, replicas) = leaderSelector.selectLeader(topicAndPartition, currentLeaderAndIsr) in PartitionStateMachine.electLeaderForPartition(...) , the replicas returned by ReassignedPartitionLeaderSelector.selectLeader() is only the new Replicas, which are then sent the LeaderAndIsrRequest. So the old replica never receives this LeaderAndIsr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)