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?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
