[
https://issues.apache.org/jira/browse/ROCKETMQ-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904265#comment-15904265
]
ASF GitHub Bot commented on ROCKETMQ-67:
----------------------------------------
Github user shroman commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/67
@Jaskey Can you explain more about this feature? Having a better
description on JIRA would help a lot review this PR -- especially for new
functionalities. Since the description is very general, I have the following
questions.
What is the advantage of introducing this strategy?
Consistent hashing could be useful if you have to move data between nodes
on broker addition/removal. But since `AllocateMessageQueueStrategy` is used by
consumers just to read from queues (if I get it right), on broker topology
change a simple rehashing works well.
Of course, consistent hashing will glue consumers to the queues they are
already consuming from as much as possible, even if topology is changed. Is
this your concern?
> Consistent Hash allocate strategy support
> -----------------------------------------
>
> Key: ROCKETMQ-67
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-67
> Project: Apache RocketMQ
> Issue Type: New Feature
> Components: rocketmq-client
> Reporter: Jaskey Lam
> Assignee: Jaskey Lam
> Fix For: 4.1.0-incubating
>
>
> For now, the average allocate strategy is very sensitive when clients
> register and unrigister.
> A Consistent Hash allocate strategy is valueable for the developer who cares
> more about stabilization than averaging.
> This option should be supported. And averaging should be meet as much as
> possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
