[jira] [Updated] (KAFKA-15835) Group commit/callbacks triggering logic

["David Jacot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-15835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jacot updated KAFKA-15835:
--------------------------------
        Parent:     (was: KAFKA-14048)
    Issue Type: Improvement  (was: Sub-task)

> Group commit/callbacks triggering logic
> ---------------------------------------
>
>                 Key: KAFKA-15835
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15835
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, consumer
>            Reporter: Lianet Magrans
>            Assignee: Lianet Magrans
>            Priority: Major
>              Labels: kip-848-client-support, reconciliation
>
> The new consumer reconciliation logic triggers a commit request, revocation callback and assignment callbacks sequentially to ensure that they are executed in that order. This means that we could require multiple iterations of the poll loop to complete reconciling an assignment. 
> We could consider triggering them all together, to be executed in the same poll iteration, while still making sure that they are executed in the right order. Note that the sequence sometimes should not block on failures (ex. if commit fails revocation proceeds anyways), and other times it does block (if revocation callbacks fail onPartitionsAssigned is not called).
> As part of this task, review the time boundaries for the commit request issued when the assignment changes. It will be effectively time bounded by the rebalance timeout enforced by the broker, so initial approach is to use the same rebalance timeout as boundary on the client. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)