[
https://issues.apache.org/jira/browse/KAFKA-10560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yeva Byzek updated KAFKA-10560:
-------------------------------
Description:
This Jira is a request for AK bin command to _cleanly_ get AK cluster ID,
without going to ZooKeeper and without going to the broker logs.
Looking for an equivalent to `describeCluster` functionality in the AdminAPI,
but from an AK command.
Current workaround (quite a hack and very unpretty): enable TRACE logging and
run:
{{kafka-topics --bootstrap-server broker:9092 --list 2>&1 | grep cluster_id |
grep fetchMetadata | awk -v FS="cluster_id=" 'NF>1\{print $2}' | awk -F,
'\{print $1;}'}}
was:
This Jira is a request for AK bin command to _cleanly_ get AK cluster ID,
without going to ZooKeeper.
Looking for an equivalent to `describeCluster` functionality in the AdminAPI,
but from an AK command.
> Request for AK bin command to get AK cluster ID
> -----------------------------------------------
>
> Key: KAFKA-10560
> URL: https://issues.apache.org/jira/browse/KAFKA-10560
> Project: Kafka
> Issue Type: Improvement
> Reporter: Yeva Byzek
> Priority: Major
>
> This Jira is a request for AK bin command to _cleanly_ get AK cluster ID,
> without going to ZooKeeper and without going to the broker logs.
>
> Looking for an equivalent to `describeCluster` functionality in the AdminAPI,
> but from an AK command.
>
> Current workaround (quite a hack and very unpretty): enable TRACE logging and
> run:
>
> {{kafka-topics --bootstrap-server broker:9092 --list 2>&1 | grep cluster_id |
> grep fetchMetadata | awk -v FS="cluster_id=" 'NF>1\{print $2}' | awk -F,
> '\{print $1;}'}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
