[GitHub] [rocketmq] lushilin opened a new issue #3603: Fetch or Commit ConsumeOffset may not use master broker firstly

[GitBox]

lushilin opened a new issue #3603:
URL: https://github.com/apache/rocketmq/issues/3603


   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
![image](https://user-images.githubusercontent.com/17663472/145169456-7ed12156-fa80-4a0d-a101-2aec6d41529d.png)
   如果一组brokerSet的组成是master节点(brokerId=0), 
slave节点(brokerId=16)，那么在hashMap遍历的时候，不一定会先遍历到master节点，因为hashMap的初始化capacity默认是16，0和16的hashcode
 % 16都为0，所以遍历的时候是不保序的。
   会导致在主节点存活的情况下，提交或者初始化拉取offset都从slave节点进行提交或者拉取。


-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org