xiaobing395845388 commented on issue #1269: Disscuss about hash algorithm in message queue selector ,dev URL: https://github.com/apache/rocketmq/pull/1269#issuecomment-513695312 > @xiaobing395845388 Thanks for your contribution, and last comment means that it would be nice if you can provide more verification, not only in the performance but also make sure that there's no compatibility (maybe lead to hashed another queue after upgraded to this new version client) issue, and I will reopen this pr for convenient. I had accepted what you are worrying about. About history message before and new message using this algorithm. But the algorithm before, for example config queues of topic 32 ,then config 128 example code indexForQueue(32, "a283c3d1616d4de39424da4a47e4b620") return 5 indexForQueue(128, "a283c3d1616d4de39424da4a47e4b620") return 69 this cased same key select different queue but by the algorithm i commited, same key always be sended to the same queue Can this both selector be lived and client choose one to use in different sence?
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
