[
https://issues.apache.org/jira/browse/ROCKETMQ-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15970965#comment-15970965
]
ASF GitHub Bot commented on ROCKETMQ-175:
-----------------------------------------
Github user Jaskey commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/92
@vsair
What I mean is that the scene this pr is going to fix is breaking the
restrict that the same consumer group has the same subscriptions.
Though this may help improve the refresh the subscriptions, but the same
problem is still there remains no solution in the existing design.
IMO, we should solve this problem directly to solve all the related
problem. Which is issued in https://issues.apache.org/jira/browse/ROCKETMQ-94
> Consumer may miss messages because of inconsistent subscription
> ---------------------------------------------------------------
>
> Key: ROCKETMQ-175
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-175
> Project: Apache RocketMQ
> Issue Type: Bug
> Components: rocketmq-broker
> Affects Versions: 4.0.0-incubating
> Reporter: Eric Liu
> Assignee: yukon
> Fix For: 4.1.0-incubating
>
>
> When consumers in one group have different subscriptions(with tag), broker
> will select the one has latest client version. Although when this consumer
> shutdown, broker would not update the subscription until someone in group
> restart, so other consumers will miss messages by the dead consumer's tag.
> Broker should refresh the group's subscriptions when someone was off-line.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
