[
https://issues.apache.org/jira/browse/ROCKETMQ-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978469#comment-15978469
]
ASF GitHub Bot commented on ROCKETMQ-175:
-----------------------------------------
Github user dongeforever commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/92
@Jaskey It may take a long time to fix the issue ROCKETMQ-94.
And we could improve it step by step.
Now one consumer startup will refresh the subscriptions, but the consumer
shutdown does not.
This maybe confusing.
IMO, it is reasonable to refresh when rebalance occurs.
> 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: Eric Liu
> 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)
