[
https://issues.apache.org/jira/browse/KAFKA-15832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-15832:
------------------------------
Priority: Critical (was: Major)
> Trigger client reconciliation based on manager poll
> ---------------------------------------------------
>
> Key: KAFKA-15832
> URL: https://issues.apache.org/jira/browse/KAFKA-15832
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lucas Brutschy
> Priority: Critical
> Labels: kip-848-client-support, reconciliation
> Fix For: 3.8.0
>
>
> Currently the reconciliation logic on the client is triggered when a new
> target assignment is received and resolved, or when new unresolved target
> assignments are discovered in metadata.
> This could be improved by triggering the reconciliation logic on each poll
> iteration, to reconcile whatever is ready to be reconciled. This would
> require changes to support poll on the MembershipManager, and integrate it
> with the current polling logic in the background thread. Receiving a new
> target assignment from the broker, or resolving new topic names via a
> metadata update could only ensure that the #assignmentReadyToReconcile is
> properly updated (currently done), but wouldn't trigger the #reconcile()
> logic, leaving that to the #poll() operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
