You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jose Armando Garcia Sancio (Jira)" <ji...@apache.org> on 2020/06/02 17:31:00 UTC
[jira] [Assigned] (KAFKA-8480) Clients may fetch incomplete set of
topic partitions during cluster startup
[ https://issues.apache.org/jira/browse/KAFKA-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jose Armando Garcia Sancio reassigned KAFKA-8480:
-------------------------------------------------
Assignee: Jose Armando Garcia Sancio (was: Anna Povzner)
> Clients may fetch incomplete set of topic partitions during cluster startup
> ---------------------------------------------------------------------------
>
> Key: KAFKA-8480
> URL: https://issues.apache.org/jira/browse/KAFKA-8480
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Anna Povzner
> Assignee: Jose Armando Garcia Sancio
> Priority: Major
>
> KafkaConsumer#partitionsFor() or AdminClient#describeTopics() may return not all partitions for a given topic when the cluster is starting up (after cluster was down).
> The cause is controller, on becoming a controller, sending UpdateMetadataRequest for all partitions with at least one online replica, and then a separate UpdateMetadataRequest for all partitions with at least one offline replica. If client sends metadata request in between broker processing those two update metadata requests, clients will get incomplete set of partitions.
> Proposed fix: controller should send one UpdateMetadataRequest (containing all partitions) in ReplicaStateMachine#startup().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)