Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-12801

High CPU load after restarting brokers subsequent to quorum loss

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.0
    • Fix Version/s: None
    • Component/s: core, KafkaConnect
    • Labels:

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gunnar.morling Gunnar Morling
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: