[
https://issues.apache.org/jira/browse/KAFKA-16375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-16375:
-----------------------------------
Description: The current implementation of the new consumer discards the
result of a reconciliation if the member rejoined, based on a comparison of the
member epoch at the start and end of the reconciliation. If the epochs changed
the reconciliation is discarded. This is not right because the member epoch
could be incremented without an assignment change. This should be fixed to
ensure that the reconciliation is discarded if the member rejoined, probably
based on a flag that truly reflects that it went through a transition to
joining. (was: The current implementation of the new consumer discards the
result of a reconciliation if the member rejoined, based on a comparison of the
member epoch at the start and end of the reconciliation. If the epochs changed
the reconciliation is discarded. This is not right because the member epoch
could be incremented without an assignment change. This should be fixed to
ensure that the reconciliation is discarded if the member rejoined, probably
based on a flag that truly reflects that it went through a transition to
joining.
As a potential improvement, consider if the member could keep the
reconciliation if it rejoined but got the same assignment.)
> Fix logic for discarding reconciliation if member rejoined
> ----------------------------------------------------------
>
> Key: KAFKA-16375
> URL: https://issues.apache.org/jira/browse/KAFKA-16375
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Critical
> Labels: kip-848-client-support
>
> The current implementation of the new consumer discards the result of a
> reconciliation if the member rejoined, based on a comparison of the member
> epoch at the start and end of the reconciliation. If the epochs changed the
> reconciliation is discarded. This is not right because the member epoch could
> be incremented without an assignment change. This should be fixed to ensure
> that the reconciliation is discarded if the member rejoined, probably based
> on a flag that truly reflects that it went through a transition to joining.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
