[
https://issues.apache.org/jira/browse/KAFKA-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658929#comment-14658929
]
Jiangjie Qin commented on KAFKA-2406:
-------------------------------------
[~ashishujjain], the large number of ISR change might not only occur during
Admin operations, for example, any long GC might cause this issue. Also when a
broker goes down if zk session timeout is longer than the
replica.lag.time.max.ms will also cause problem.
I kind of think it is OK to delay the ISR change propagation. From user point
of view, the ISR from two brokers still can be different even with the current
approach considering we have a propagation delay.
> ISR propagation should be throttled to avoid overwhelming controller.
> ---------------------------------------------------------------------
>
> Key: KAFKA-2406
> URL: https://issues.apache.org/jira/browse/KAFKA-2406
> Project: Kafka
> Issue Type: Bug
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Priority: Blocker
>
> This is a follow up patch for KAFKA-1367.
> We need to throttle the ISR propagation rate to avoid flooding in controller
> to broker traffic. This might significantly increase time of controlled
> shutdown or cluster startup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
