You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "radai rosenblatt (JIRA)" <ji...@apache.org> on 2018/03/13 17:19:00 UTC
[jira] [Updated] (KAFKA-6648) Fetcher.getTopicMetadata() only
returns "healthy" partitions, not all
[ https://issues.apache.org/jira/browse/KAFKA-6648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
radai rosenblatt updated KAFKA-6648:
------------------------------------
Fix Version/s: 2.0.0
> Fetcher.getTopicMetadata() only returns "healthy" partitions, not all
> ---------------------------------------------------------------------
>
> Key: KAFKA-6648
> URL: https://issues.apache.org/jira/browse/KAFKA-6648
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 1.0.0, 0.11.0.2
> Reporter: radai rosenblatt
> Assignee: radai rosenblatt
> Priority: Major
> Fix For: 2.0.0
>
>
> {code}
> if (!shouldRetry) {
> HashMap<String, List<PartitionInfo>> topicsPartitionInfos = new HashMap<>();
> for (String topic : cluster.topics())
> topicsPartitionInfos.put(topic, cluster.availablePartitionsForTopic(topic));
> return topicsPartitionInfos;
> }
> {code}
> this leads to inconsistent behavior upstream, for example in KafkaConsumer.partitionsFor(), where if there's valid metadata all partitions would be returned, whereas if MD doesnt exist (or has expired) a subset of partitions (only the healthy ones) would be returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)