[
https://issues.apache.org/jira/browse/ROCKETMQ-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030874#comment-16030874
]
ASF GitHub Bot commented on ROCKETMQ-203:
-----------------------------------------
GitHub user Jaskey opened a pull request:
https://github.com/apache/incubator-rocketmq/pull/109
[ROCKETMQ-203]Support client to allocate message queue in machine room
nearby priority
JIRA:
https://issues.apache.org/jira/browse/ROCKETMQ-203?jql=project%20%3D%20ROCKETMQ
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Jaskey/incubator-rocketmq
ROCKETMQ-203-machineroom-nearby-strategy
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-rocketmq/pull/109.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #109
----
commit fd756669d8f07dc02aca540218013c3f8bd6fbc7
Author: Jaskey <[email protected]>
Date: 2017-05-31T09:04:04Z
Add allocate strategy to support allocating message queues to client in
machine room nearby priority
----
> Support client to allocate message queue in machine room nearby priority
> ------------------------------------------------------------------------
>
> Key: ROCKETMQ-203
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-203
> Project: Apache RocketMQ
> Issue Type: New Feature
> Reporter: Jaskey Lam
> Assignee: vongosling
> Attachments: AVLCB%1XMJ}T_YXP[OPF){T.png
>
>
> As the picture shows, in multi-machine room acrtiture , the consumer may be
> deployed in different IDC and so do the broker.
> But the user may possiblly need to consumer message from its own IDC since it
> is near and faster. But when problem occurs say all consumers in one IDC is
> crashed, the messages can also be consumed by other consumers in other IDC.
> This is a very important feature for many users, but currently, if the user
> needs this feature, they must implement their own allocate strategy which is
> not easy and error prone.
> And, this feature should be be conflict to the existing allocate strategy
> that means the user can still choose their better allocate strategy say
> AVERAGE or AVERAGE_BY_CIRCLE, but nearby machine room will be supported
> easily too.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
