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

shizhenzhen commented on KAFKA-13226:
-------------------------------------

我在尝试修复它的时候, 我发现就算修复了KafkaZkClient#getAllBrokerAndEpochsInCluster 那里的toMap 
不排序的问题, 仍然是不能够解决这个问题的,因为在UPDATAMETADATA 
请求的时候也做了更新,会导致将之前已经排序的覆盖掉,所以UPDATAMETADATA也需要做处理, 
但是整个集群就算不是排序的,也没有什么问题,除了createTopic的时候,所以我在解决这个bug的时候,只是在createTopic那里做了一下排序,这样改动最小,可以完美的解决问题

> Partition expansion may cause uneven distribution
> -------------------------------------------------
>
>                 Key: KAFKA-13226
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13226
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 2.5.0, 2.8.0, 2.7.1, 2.6.2, 2.8.1, 3.0.0
>         Environment: mac  
> kafka-2.5.0
>            Reporter: shizhenzhen
>            Priority: Major
>
>  
>  {color:#ff0000}*Partition expansion may cause uneven distribution*{color}
>  
> 1. Create a Topic  , 3-partition   1-replical
> !https://img-blog.csdnimg.cn/561112064b114acfb03882aa09100e0e.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_Q1NETiBA55-z6Ie76Ie755qE5p2C6LSn6ZO6,size_55,color_FFFFFF,t_70,g_se,x_16!
>  
> 2. partition expansion to 5 - partiton
> !https://img-blog.csdnimg.cn/f7c3c33b6662457080d9bb5bb190c0c2.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_Q1NETiBA55-z6Ie76Ie755qE5p2C6LSn6ZO6,size_49,color_FFFFFF,t_70,g_se,x_16!
>  
> 3. Does this meet expectations ?
>  
> !https://img-blog.csdnimg.cn/20cc1007c4214c4ebfcb1b2c2eeb98e4.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_Q1NETiBA55-z6Ie76Ie755qE5p2C6LSn6ZO6,size_18,color_FFFFFF,t_70,g_se,x_16!
>  
> {color:#ff0000}*so this is a bug ?*{color}
>  
> The problem may arise here ; 
> When we create a new topic .  get the broker list is a Object Map ; 
> *This is disordered*
> you can read the code , first it have sortBy brokerId, but finally it convert 
> to a *disorde Map;*
>  
>  
> !https://img-blog.csdnimg.cn/131b9bf0c19e4753a73512af4c9c5854.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_Q1NETiBA55-z6Ie76Ie755qE5p2C6LSn6ZO6,size_66,color_FFFFFF,t_70,g_se,x_16!
>  
>  
>  
> The important thing is that it has been sorted when expanding the partition 
> and parition-reassignment ;   
> {color:#ff0000}*So why not sort when creating topics?*{color}
>  
> If the topic is sorted when  create a new topic , this problem will not occur 
> ;
>  
> so it maybe is a tiny bug ?
>  
>  
> if you can read Chinese ,
> You can look at this article. I describe it in detail
>  
> We look forward to receiving your reply
>  
> 如果你能看懂中文,可以看看这篇文章 我描述的很详细! 
>  [This may be a Kafka 
> bug?|[https://shirenchuang.blog.csdn.net/article/details/119912418]]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to