[jira] [Commented] (KAFKA-8179) Incremental Rebalance Protocol for Kafka Consumer

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844393#comment-16844393 ] 

ASF GitHub Bot commented on KAFKA-8179:
---------------------------------------

guozhangwang commented on pull request #6778: KAFKA-8179: Part 2, ConsumerCoordinator Algorithm [WIP]
URL: https://github.com/apache/kafka/pull/6778
 
 
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Incremental Rebalance Protocol for Kafka Consumer
> -------------------------------------------------
>
>                 Key: KAFKA-8179
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8179
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer
>            Reporter: Guozhang Wang
>            Assignee: Guozhang Wang
>            Priority: Major
>
> Recently Kafka community is promoting cooperative rebalancing to mitigate the pain points in the stop-the-world rebalancing protocol. This ticket is created to initiate that idea at the Kafka consumer client, which will be beneficial for heavy-stateful consumers such as Kafka Streams applications.
> In short, the scope of this ticket includes reducing unnecessary rebalance latency due to heavy partition migration: i.e. partitions being revoked and re-assigned. This would make the built-in consumer assignors (range, round-robin etc) to be aware of previously assigned partitions and be sticky in best-effort.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)