[
https://issues.apache.org/jira/browse/BOOKKEEPER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527679#comment-13527679
]
Sijie Guo commented on BOOKKEEPER-256:
--------------------------------------
1. A publishes A1. A1 arrives B, but delayed at C.
A: [A: 1, B: 0, C: 0]
B: [A: 1, B: 0, C: 0]
C: [A: 0, B: 0, C: 0]
2. B publishes B1. B1 carries remote seq ids : [A: 1, B: 1, C: 0]. A & C's last
seq id would be updated as:
A: [A: 1, B: 1, C: 0]
C: [A: 0, B: 1, C: 0]
3. A1 arrives at C. C's last seq id would be updated as
C: [A: 1, B: 1, C: 0]
for C's subscriber, it would receive B1 as [A: 0, B: 1, C: 0](localseqid=1) and
A1 as [A: 1, B: 1, C: 0](localseqid=2).
the subscriber could be notified B1 is the first message from region B, and A1
is the first message from region A. I think it works correctly.
> Update remote component sequence IDs only for messages from the source region
> -----------------------------------------------------------------------------
>
> Key: BOOKKEEPER-256
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-256
> Project: Bookkeeper
> Issue Type: Improvement
> Components: hedwig-server
> Affects Versions: 4.0.0, 4.1.0
> Reporter: Aniruddha
> Assignee: Aniruddha
> Priority: Minor
> Fix For: 4.2.0
>
> Attachments: BK-256.patch, BK-256.patch, BK-256-v1.patch,
> BK-256-v2.patch
>
>
> In the current setup, remote components for a message being persisted don't
> give any meaningful information about the number of messages the hub has
> received for that topic from other regions. The provided patch fixes this by
> updating the remote component of the locally persisted message for a region X
> only if the message received by the RegionManager originates from region X.
> Edit - You can take a look at the discussion at
> http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201205.mbox/%3cCAOLhyDTEm5=p8emd8xmvcy_6ktb40rqx6dwwy50arbaebdg...@mail.gmail.com%3e
> for context.
> Review board link : https://reviews.apache.org/r/6789/
--
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
