You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "Jaskey Lam (JIRA)" <ji...@apache.org> on 2017/05/31 06:03:04 UTC

[jira] [Updated] (ROCKETMQ-203) Support client to allocate message queue in machine room nearby priority

     [ https://issues.apache.org/jira/browse/ROCKETMQ-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaskey Lam updated ROCKETMQ-203:
--------------------------------
    Summary: Support client to allocate message queue in machine room nearby priority  (was: Support client to allocate message qUEUE 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)