You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2020/12/02 09:37:00 UTC

[jira] [Assigned] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions

     [ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chia-Ping Tsai reassigned KAFKA-10794:
--------------------------------------

    Assignee: limeng

> Replica leader election is too slow in the case of too many partitions
> ----------------------------------------------------------------------
>
>                 Key: KAFKA-10794
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10794
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.6.0, 2.5.1
>            Reporter: limeng
>            Assignee: limeng
>            Priority: Major
>         Attachments: clipboard_image_1606806581629.png, image-2020-12-02-15-23-43-384.png, 截屏2020-12-01 下午2.36.19.png, 截屏2020-12-02 上午11.43.48.png
>
>
> There is more than 6000 topics and 300 brokers in my kafka cluster, and we frequently run kafka-preferred-replica-election.sh to rebalance our cluster. But the reblance process spendes too more time and cpu resource like the picture blow.
> We find that the function:'controllerContext.allPartitions' is invoked too many times.
> !截屏2020-12-02 上午11.43.48.png!
> !image-2020-12-02-15-23-43-384.png!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)