apalan60 commented on PR #20689:
URL: https://github.com/apache/kafka/pull/20689#issuecomment-3394072288
I also checked the test coverage for this field.
There’s an existing test, `testListNodesWithFencedBroker`, which already
covers the `DescribeCluster(includeFencedBrokers=true)` case.
It verifies that when a broker is shut down for a while, the
`DescribeCluster` correctly reports that broker with `isFenced=true`.
In addition, I manually verified the behavior using the CLI tool.
After stopping one broker, the `kafka-cluster.sh list-endpoints
--include-fenced-brokers` command correctly shows that the broker is marked as
`STATE=fenced`:
```
./bin/kafka-cluster.sh list-endpoints \
--bootstrap-server localhost:29092 \
--include-fenced-brokers
ID HOST PORT RACK STATE ENDPOINT_TYPE
4 localhost 29092 null unfenced broker
5 localhost 39092 null fenced broker
6 localhost 49092 null unfenced broker
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
