[
https://issues.apache.org/jira/browse/BOOKKEEPER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175944#comment-13175944
]
Flavio Junqueira commented on BOOKKEEPER-147:
---------------------------------------------
In my interpretation, this issue questions the necessity of implementing a
protocol on top of hedwig as you suggest, Ben, to implement this functionality.
The rationale is that the published messages in rA are guaranteed to be
available at the time we subscribe to the same topic in rB, so why can't we
simply have a way to bring those messages to region rB before rB takes new
publishes for topic T?
I believe the point you're getting into is that an implementation for this
special case does not generalize assuming multiple subscribers for the same
topic in a single region. I tend to agree that it is not clear that it pays off
to have this extra complexity given that the application-level protocol you
propose is relatively simple.
> 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
