Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-6117

Unregister Kafka nodes when scaling down

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.8.0.GA
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Apparently, the Kafka nodes should be unregistered using the Kafka Admin API when scaling-down. Without that, the cluster will still expect them to be present and for example be unable to handle the metadata upgrade:

      2024-07-03 12:50:18 INFO KRaftMetadataManager:165 - Reconciliation #663(timer) Kafka(myproject/my-cluster): Updating metadata version from 3.6-IV2 to 3.7-IV4
2024-07-03 12:50:18 WARN KRaftMetadataManager:124 - Reconciliation #663(timer) Kafka(myproject/my-cluster): Failed to update metadata version to 3.7 (the current version is 3.6-IV2)
org.apache.kafka.common.errors.InvalidUpdateVersionException: Invalid update version 19 for feature metadata.version. Broker 1002 only supports versions 1-14

      This would be simple to implement for regular scale-downs. But will be non-trivial for node pool deletions.

      Created by Strimzi#10296

              Unassigned Unassigned
              scholzj JAkub Scholz
              Lukas Kral Lukas Kral
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: