[jira] [Updated] (KAFKA-19276) Compare assignment configuration only when assignment related configurations are updated

["Lucas Brutschy (Jira)" <ji...@apache.org>]

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

Lucas Brutschy updated KAFKA-19276:
-----------------------------------
    Priority: Minor  (was: Major)

> Compare assignment configuration only when assignment related configurations are updated
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-19276
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19276
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Lucas Brutschy
>            Assignee: Uladzislau Blok
>            Priority: Minor
>
> In KIP-1071, there are configurations that affect the assignment, and that can be configured dynamically. Those are:
>  * streams.num.standby.replicas
>  * streams.assignor.name
>  * streams.num.warmup.replicas
>  * streams.acceptable.recovery.lag
> However, only the first one is currently implemented.
> We should implement a generic mechanism to trigger a rebalance on the next heartbeat into a streams group, when any of the above group-level configurations have been changed.
>  
> Triggering a rebalance would mean setting the `bumpGroupEpoch` flag here: [https://github.com/apache/kafka/blob/trunk/group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupMetadataManager.java#L1933]
>  
> Detecting a group config change would probably happen here:
> [https://github.com/apache/kafka/blob/trunk/group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupConfigManager.java#L58]
>  



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