[
https://issues.apache.org/jira/browse/KAFKA-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-15843:
-----------------------------------
Description:
Legacy coordinator triggers onPartitionsAssigned with empty assignment (which
is not the case when triggering onPartitionsRevoked or Lost). This is the
behaviour of the legacy coordinator, and the new consumer implementation
maintains the same principle. We should review this to fully understand if it
is really needed to call onPartitionsAssigned with empty assignment (or if it
should behave consistently with the onRevoke/Lost).
Note that the consumer integration tests rely on this call to
onPartitionsAssigned to #awaitRebalance (AbstractConsumerTest.scala)
was:Legacy coordinator triggers onPartitionsAssigned with empty assignment
(which is not the case when triggering onPartitionsRevoked or Lost). This is
the behaviour of the legacy coordinator, and the new consumer implementation
maintains the same principle. We should review this to fully understand if it
is really needed to call onPartitionsAssigned with empty assignment (or if it
should behave consistently with the onRevoke/Lost)
> Review consumer onPartitionsAssigned called with empty partitions
> -----------------------------------------------------------------
>
> Key: KAFKA-15843
> URL: https://issues.apache.org/jira/browse/KAFKA-15843
> 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-e2e,
> kip-848-preview
> Fix For: 3.8.0
>
>
> Legacy coordinator triggers onPartitionsAssigned with empty assignment (which
> is not the case when triggering onPartitionsRevoked or Lost). This is the
> behaviour of the legacy coordinator, and the new consumer implementation
> maintains the same principle. We should review this to fully understand if it
> is really needed to call onPartitionsAssigned with empty assignment (or if it
> should behave consistently with the onRevoke/Lost).
> Note that the consumer integration tests rely on this call to
> onPartitionsAssigned to #awaitRebalance (AbstractConsumerTest.scala)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
