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

Ziyun Fu updated KAFKA-21391:
-----------------------------
    Description: 
In the rack-aware sticky assignor, we are planning to priorize rack ahead of 
stickiness. 

There will be 4 steps, 
 # assign the standby task to previous holder who is rack-diverse
 # assign the standby task to the least-loaded rack-diverse member
 # assign it to a previous holder
 # assignor it to the least-loaded member

In step 2, member A and B are both the same level rack diverse to task1, if A 
has least-loaded then B, we assign task1 to A. But there's cases that A is 
actually the previous member for task2, then in step 3 for task2, A could not 
able to hold back task2 because it's holding task1. If we are able to assign 
task1 to B then we will not lose rack diversity and at the same time improve 
stickiness 

> Improve standby stickiness of rack-aware standby placement in the sticky task 
> assignor  
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-21391
>                 URL: https://issues.apache.org/jira/browse/KAFKA-21391
>             Project: Kafka
>          Issue Type: Improvement
>          Components: group-coordinator, streams
>            Reporter: Ziyun Fu
>            Assignee: Ziyun Fu
>            Priority: Major
>
> In the rack-aware sticky assignor, we are planning to priorize rack ahead of 
> stickiness. 
> There will be 4 steps, 
>  # assign the standby task to previous holder who is rack-diverse
>  # assign the standby task to the least-loaded rack-diverse member
>  # assign it to a previous holder
>  # assignor it to the least-loaded member
> In step 2, member A and B are both the same level rack diverse to task1, if A 
> has least-loaded then B, we assign task1 to A. But there's cases that A is 
> actually the previous member for task2, then in step 3 for task2, A could not 
> able to hold back task2 because it's holding task1. If we are able to assign 
> task1 to B then we will not lose rack diversity and at the same time improve 
> stickiness 



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to