Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Sat, 24 Sep 2016 14:34:20 +0000 (UTC)
From: "Ben Stopford (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.13007368.1474727638000.656013.1474727660426@Atlassian.JIRA>
In-Reply-To: <JIRA.13007368.1474727638000@Atlassian.JIRA>
References: <JIRA.13007368.1474727638000@Atlassian.JIRA> <JIRA.13007368.1474727638220@arcas>
Subject: [jira] [Created] (KAFKA-4216) Replication Throttling: Leader may
 not be throttled if it is not "moving"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 24 Sep 2016 14:34:22 -0000

Ben Stopford created KAFKA-4216:
-----------------------------------

             Summary: Replication Throttling: Leader may not be throttled if it is not "moving"
                 Key: KAFKA-4216
                 URL: https://issues.apache.org/jira/browse/KAFKA-4216
             Project: Kafka
          Issue Type: Bug
    Affects Versions: 0.10.1.0
            Reporter: Ben Stopford
            Assignee: Ben Stopford


The current algorithm in kafka-reassign-partitions applies a throttle to all moving replicas, be they leader-side or follower-side. 

The problem is that the leader may not be moving, which would mean it would not have a throttle applied. So the throttle should be applied to:
[all existing replicas] ++  [all proposed replicas that moved]

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