[
https://issues.apache.org/jira/browse/KAFKA-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659007#comment-14659007
]
Jun Rao commented on KAFKA-2406:
--------------------------------
[~singhashish], yes, ideally we want to propagate isr asap. However, this is
not critical for the current known use cases. The first use case is for admin
tools like describing a topic. The second potential use case is for read
affinity in the consumer, which is just an optimization. For both cases,
delaying the propagation of isr is ok. Also, isr typically only changes during
rolling bounces. If you turn off and delay the propagation then, most of the
isr changes will be delayed anyway.
We can probably have a configurable batching window on the broker side.
> 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)
