[
https://issues.apache.org/jira/browse/KAFKA-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans resolved KAFKA-15539.
------------------------------------
Resolution: Duplicate
> Client should stop fetching while partitions being revoked
> ----------------------------------------------------------
>
> Key: KAFKA-15539
> URL: https://issues.apache.org/jira/browse/KAFKA-15539
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
> Labels: kip-848, kip-848-client-support, kip-848-preview
>
> When partitions are being revoked (client received revocation on heartbeat
> and is in the process of invoking the callback), we need to make sure we do
> not fetch from those partitions anymore:
> * no new fetches should be sent out for the partitions being revoked
> * no fetch responses should be handled for those partitions (case where a
> fetch was already in-flight when the partition revocation started.
> This does not seem to be handled in the current KafkaConsumer and the old
> consumer protocol (only for the EAGER protocol).
> Consider re-using the existing pendingRevocation logic that already exist in
> the subscriptionState & used from the fetcher to determine if a partition is
> fetchable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
