[
https://issues.apache.org/jira/browse/KAFKA-12801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348804#comment-17348804
]
Gunnar Morling commented on KAFKA-12801:
----------------------------------------
Ok, so I've added the two JFR recordings to my example repository
(https://github.com/gunnarmorling/debezium-examples/commit/e6ce9f2db398ee042e9cc0e611310eeddf3c9427),
which also contains the set-up for reproducing this.
> 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
>
> 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.3.4#803005)
