...
When a KRaft broker node shuts down, it is "unfencedfenced", but still registered in the controller. To completely remove KRaft-based broker nodes, they must first be unregistered via the Kafka Admin API.
...
The console tool used for describing metadata quorum’s status will be updated with a new option, --include-inactive-observers. When used with --status argument for the describe command, it will return inactive observers as InactiveObservers. When used with --replication argument, it will include the replication state of inactive observers, based on the last known state known by the leader.
Example:
| Code Block | ||
|---|---|---|
| ||
/bin/kafka-metadata-quorum.sh --bootstrap-controller localhost:9093 describe --status –include-inactive-observers ClusterId: hNWu1PEBT9ONqOc1kOeb7g LeaderId: 1 LeaderEpoch: 15 HighWatermark: 130383 MaxFollowerLag: 0 MaxFollowerLagTimeMs: 0 CurrentVoters: [0,1,2] CurrentObservers: [3,4] InactiveObservers: [5] → (Broker 5 has shutdown but still registered) /bin/kafka-metadata-quorum.sh --bootstrap-controller localhost:9093 describe --status ClusterId: hNWu1PEBT9ONqOc1kOeb7g LeaderId: 1 LeaderEpoch: 15 HighWatermark: 130383 MaxFollowerLag: 0 MaxFollowerLagTimeMs: 0 CurrentVoters: [0,1,2] CurrentObservers: [3,4] |
...