You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2019/05/28 19:02:00 UTC

[jira] [Created] (KAFKA-8442) Inconsistent ISR output in topic command when using --bootstrap-server

Jason Gustafson created KAFKA-8442:
--------------------------------------

             Summary: 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


If there is no leader for a partition, the Metadata API returns an empty set of replicas and 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.3#76005)