[
https://issues.apache.org/jira/browse/KAFKA-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658968#comment-14658968
]
Jiangjie Qin commented on KAFKA-2406:
-------------------------------------
[~junrao], I was thinking to have a sequential path for each broker before, but
it probably does not make sense. So a global sequential zk path should be good
enough.
And I agree that a periodically checking thread might be a bad idea. The main
concern I have is that what if there are many brokers and they report isr
change almost at same time, will the watcher be fired for that many times? Will
that cause problem on controller?
Deleting the zk path on controller migration makes sense and I'm actually
manually doing it now. The only issue I see here is that when I was trying to
delete the zk path with > 110000 children paths, it takes quite a while. Not
sure if that will cause issue.
> 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)
