[
https://issues.apache.org/jira/browse/KAFKA-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934231#comment-16934231
]
Viktor Somogyi-Vass commented on KAFKA-6393:
--------------------------------------------
Hey Jason, if you don't mind I'll pick this up and write a KIP. As I see most
of the API calls are available. I've been also thinking to do a rolling restart
admin client call which tells the controller to restart the brokers and then
itself so we'll avoid unnecessary reelections. Do you think it's a good idea?
Are there anything else that we should add?
> Add tool to view active brokers
> -------------------------------
>
> Key: KAFKA-6393
> URL: https://issues.apache.org/jira/browse/KAFKA-6393
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Jason Gustafson
> Priority: Major
> Labels: needs-kip
>
> It would be helpful to have a tool to view the active brokers in the cluster.
> For example, it could include the following:
> 1. Broker id and version (maybe detected through ApiVersions request)
> 2. Broker listener information
> 3. Whether broker is online
> 4. Which broker is the active controller
> 5. Maybe some key configs (e.g. inter-broker version and message format
> version)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
