[jira] [Commented] (KAFKA-12801) High CPU load after restarting brokers subsequent to quorum loss

["Colin McCabe (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-12801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17452677#comment-17452677 ] 

Colin McCabe commented on KAFKA-12801:
--------------------------------------

Does this still happen with 3.0?

> High CPU load after restarting brokers subsequent to quorum loss
> ----------------------------------------------------------------
>
>                 Key: KAFKA-12801
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12801
>             Project: Kafka
>          Issue Type: Bug
>          Components: core, KafkaConnect
>    Affects Versions: 2.8.0
>            Reporter: Gunnar Morling
>            Priority: Major
>              Labels: kip-500
>
> I'm testing Kafka in the new KRaft mode added in 2.8. I have a cluster of three Kafka nodes (all combined nodes), and one Kafka Connect node. After starting all components, I first stop the current controller of the Kafka cluster, then I stop the then controller of the Kafka cluster. At this point, only one Kafka node out of the original three and Connect is running.
> When now restarting the two stopped Kafka nodes, CPU load on the Connect node and the two broker nodes goes up to 100% and remains at that level for an indefinite amount of time.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)