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/02/13 12:55:41 UTC
[jira] [Created] (ROCKETMQ-94) Support different subscriptions for
some newly release instance
Jaskey Lam created ROCKETMQ-94:
----------------------------------
Summary: Support different subscriptions for some newly release instance
Key: ROCKETMQ-94
URL: https://issues.apache.org/jira/browse/ROCKETMQ-94
Project: Apache RocketMQ
Issue Type: New Feature
Components: rocketmq-broker, rocketmq-client
Affects Versions: 4.0.0-incubating
Reporter: Jaskey Lam
Assignee: yukon
RocketMQ 's consumer group has a restrict that all instances must have the same subcriptions.
But when new version is release, the subcriptions may be added or removed, which will make all instances have different subcriptions.
Say I have a app with 3 instances which subcribe topicA and topicB,which is working fine.
When I am going to release a newer version which need to subcrbe one more topicC, and when I deploy one instance, this will break the rule since it is still the same consumer group.
The same problem when I need a subcribe one more tag.
This is a very common scenario which rocketmq should support.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)