[
https://issues.apache.org/jira/browse/BOOKKEEPER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175875#comment-13175875
]
Benjamin Reed commented on BOOKKEEPER-147:
------------------------------------------
subscriptions do not move across regions. there are many issues with trying to
handle this situation on the server side that all boil down to either the lack
of total order across region or the garbage collection of messages for which
there is no subscriber.
we do have an application in yahoo that needs a similar functionality. they
handle it at the application layer by having s1:
1) reconnecting to T in rA and establishing a new subscription in rB.
2) enabling message delivery for subscription from rA
3) publishing a move message to T in rA.
4) all regions will acknowledge the move message by publishing a move ack
message to T.
5) once the move ack message is received from all regions, the client shuts
down the subscription in rA and enables delivery in rB
> Remote subscriptions do not receive all unconsumed messages for a topic
> -----------------------------------------------------------------------
>
> Key: BOOKKEEPER-147
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-147
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Fix For: 4.1.0
>
>
> Take the case of 2 regions, rA & rB and a topic T, and a mobile subscriber,
> s1. s1 could be a phone or a tablet etc.
> s1 subscribes to T on rA at time X. s1 moves location, so that rB is now it's
> local region. s1 subscribes to T on rB (the connection to rA was lost while
> moving) at time Y.
> Any messages published to T in the period between X and Y, if they have not
> been sent to s1 will not be sent to s1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
