[
https://issues.apache.org/jira/browse/KAFKA-8442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gustafson resolved KAFKA-8442.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.4.0
> Inconsistent ISR output in topic command when using --bootstrap-server
> ----------------------------------------------------------------------
>
> Key: KAFKA-8442
> URL: https://issues.apache.org/jira/browse/KAFKA-8442
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: huxihx
> Priority: Major
> Fix For: 2.4.0
>
>
> If there is no leader for a partition, the Metadata API returns an empty ISR.
> When using the `--bootstrap-server` option with `kafka-topics.sh`, this leads
> to the following output:
> {code}
> Topic:foo PartitionCount:1 ReplicationFactor:2
> Configs:segment.bytes=1073741824
> Topic: foo Partition: 0 Leader: none Replicas: 1,3 Isr:
> {code}
> When using `--zookeeper`, we display the current ISR correctly:
> {code}
> Topic:foo PartitionCount:1 ReplicationFactor:2 Configs:
> Topic: foo Partition: 0 Leader: -1 Replicas: 1,3 Isr: 1
> {code}
> To avoid confusion, we should make this output consistent or at least not
> misleading. We should either change the Metadata API to print the ISR when we
> have it or we can change the output of the topic command to `N/A` or
> something like that.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
