[
https://issues.apache.org/jira/browse/ROCKETMQ-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968566#comment-15968566
]
Jaskey Lam commented on ROCKETMQ-94:
------------------------------------
[~Yukon][~vongosling]
What's the plan for this problem? This limit rocketmq to adapt most of the
scenes
> 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 to subscribe or remove some tags.
> 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)
