You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2012/10/16 18:45:03 UTC
[jira] [Commented] (BOOKKEEPER-256) Update remote component
sequence IDs only for messages from the source region
[ https://issues.apache.org/jira/browse/BOOKKEEPER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477144#comment-13477144 ]
Ivan Kelly commented on BOOKKEEPER-256:
---------------------------------------
This patch looks like it's really to go in except for one question about one comment on reviewboard. [~i0exception] Could you take a look at the question, and then we could get this pushed in? (also may need a rebase).
Tests look good btw :)
> 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_6ktB40RQx6dWWY50ARbAEbdgtsQ@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