[
https://issues.apache.org/jira/browse/BOOKKEEPER-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673102#comment-13673102
]
ruoyiqing commented on BOOKKEEPER-616:
--------------------------------------
hum, not totally correct.
the consumer cluster is indeed a hub-side concept.every client in the same
consumer cluster will subscribe to same topic and use same subid.
For your example above, it will go like this:
there are three clients A、B 、C. they all subscribe to same topic T,but A & B
with subid S1, C with subid S2.
for hub server,he will consider client A and B as a consumer cluster C1,
consider client C as a consumer cluster C2.
1.A subscribes to topic T with subid S1
2.B subscribes to topic T with subid S1
3.C subscribes to topic T with subid S2
4.M1 is published to T, hub sends to A ans C
5.M2 is published to T, hub sends to B and C
6.M3 is published to T, hub sends to A and C
so,all messages published to topic T will be sent to C, while A and B will
receive these messages in a alternative manner.
> Add Queue Semantic for Hedwig
> -----------------------------
>
> Key: BOOKKEEPER-616
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-616
> Project: Bookkeeper
> Issue Type: New Feature
> Components: hedwig-client, hedwig-server
> Reporter: Jiannan Wang
> Attachments: Design for Message Queue Model .pdf
>
>
> Add message queue semantic to enlarge Hedwig's feature sets.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
