[
https://issues.apache.org/jira/browse/KAFKA-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587404#comment-15587404
]
ASF GitHub Bot commented on KAFKA-4313:
---------------------------------------
GitHub user junrao opened a pull request:
https://github.com/apache/kafka/pull/2043
KAFKA-4313: ISRs may thrash when replication quota is enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/junrao/kafka kafka-4313
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2043.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2043
----
commit 4fd876cc82b8ff5b455ecde8cb4a97fc3cf18c75
Author: Jun Rao <[email protected]>
Date: 2016-10-19T02:07:16Z
KAFKA-4313: ISRs may thrash when replication quota is enabled
----
> ISRs may thrash when replication quota is enabled
> -------------------------------------------------
>
> Key: KAFKA-4313
> URL: https://issues.apache.org/jira/browse/KAFKA-4313
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.1.0
> Reporter: Jun Rao
> Assignee: Jun Rao
> Fix For: 0.10.1.1
>
>
> I created a high volume topic and a low volume topic, each with 1000
> partitions and 2 replicas on 2 brokers. I populated the high volume topic
> with 4GB of data. Added a third broker and ran the rebalance tool with a
> 2MB/sec replication quota. At some point, all replicas for the low volume
> topic have been moved over and the new replicas are all in sync, but the high
> volume replicas are still catching up. Then, I started slowly producing to
> the low volume topic. Once I do that, I started seeing the low volume
> partitions' ISR constantly expanding and shrinking. The observed ISR change
> rate is ~ 6/sec. So, it does seem that ISR thrashing can happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
