[
https://issues.apache.org/jira/browse/KAFKA-16107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-16107:
------------------------------
Priority: Critical (was: Major)
> Ensure consumer does not start fetching from added partitions until
> onPartitionsAssigned completes
> --------------------------------------------------------------------------------------------------
>
> Key: KAFKA-16107
> URL: https://issues.apache.org/jira/browse/KAFKA-16107
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Critical
> Labels: kip-848-client-support, reconciliation
> Fix For: 3.8.0
>
>
> In the new consumer implementation, when new partitions are assigned, the
> subscription state is updated and then the #onPartitionsAssigned triggered.
> This sequence seems sensible but we need to ensure that no data is fetched
> until the onPartitionsAssigned completes (where the user could be setting the
> committed offsets it want to start fetching from).
> We should pause the partitions newly added partitions until
> onPartitionsAssigned completes, similar to how it's done on revocation to
> avoid positions getting ahead of the committed offsets.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
