[ 
https://issues.apache.org/jira/browse/ROCKETMQ-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968708#comment-15968708
 ] 

ASF GitHub Bot commented on ROCKETMQ-175:
-----------------------------------------

GitHub user vsair opened a pull request:

    https://github.com/apache/incubator-rocketmq/pull/92

    [ROCKETMQ-175] Consumer may miss messages because of inconsistent sub…

    For push mode, update subscription version when rebalance result changed, 
then send heart beat to broker immediately.
    
    Maybe subscriptions management mechanism could be re-designed to meet more 
complicated scenarios. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vsair/incubator-rocketmq ROCKETMQ-175

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-rocketmq/pull/92.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #92
    
----
commit 61901647fb1851bbb36b4734195206a364a0c0bd
Author: vsair <[email protected]>
Date:   2017-04-14T06:47:00Z

    [ROCKETMQ-175] Consumer may miss messages because of inconsistent 
subscription
    1. For push mode, update subscription version when rebalance result changed.

----


> 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)

Reply via email to