You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/07 16:28:00 UTC

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

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

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

guozhangwang commented on pull request #7386: KAFKA-8179: Part 7, cooperative rebalancing in Streams
URL: https://github.com/apache/kafka/pull/7386
 
 
   
 
----------------------------------------------------------------
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
(v8.3.4#803005)