You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "vongosling (JIRA)" <ji...@apache.org> on 2017/03/29 07:16:41 UTC
[jira] [Updated] (ROCKETMQ-94) Support different subscriptions for
some newly release instance
[ https://issues.apache.org/jira/browse/ROCKETMQ-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vongosling updated ROCKETMQ-94:
-------------------------------
Priority: Critical (was: Major)
> 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
> Priority: Critical
>
> RocketMQ 's consumer group has a restrict that all instances must have the same subcriptions.
> But when new version is release, the consumer's 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 instance-1, 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 solve in a transparent way.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)