[
https://issues.apache.org/jira/browse/BOOKKEEPER-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220074#comment-13220074
]
Hudson commented on BOOKKEEPER-74:
----------------------------------
Integrated in bookkeeper-trunk #384 (See
[https://builds.apache.org/job/bookkeeper-trunk/384/])
BOOKKEEPER-74: Bookkeeper Persistence Manager should give up topic on error
(sijie via ivank) (Revision 1295571)
Result = ABORTED
ivank :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/hedwig-server/src/main/java/org/apache/hedwig/server/persistence/BookkeeperPersistenceManager.java
*
/zookeeper/bookkeeper/trunk/hedwig-server/src/test/java/org/apache/hedwig/server/integration/TestHedwigHub.java
*
/zookeeper/bookkeeper/trunk/hedwig-server/src/test/java/org/apache/hedwig/server/persistence/BookKeeperTestBase.java
> Bookkeeper Persistence Manager should give up topic on error
> ------------------------------------------------------------
>
> Key: BOOKKEEPER-74
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-74
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Sijie Guo
> Fix For: 4.1.0
>
> Attachments: BK-74.patch, BK-74.patch_v2
>
>
> There are a couple of problematic cases to deal with:
> i)Other region is pushing messages faster that my bookkeeper can handle it
> (unlikely, but we should have an answer for
> this setting)
> ii) If there is an error from BK while persisting messages, we cannot
> continue (because the ordering gurantee might be
> violated). In this case, the BK layer should give up the topic.
> To retain ordering guarantees, this should be done below the Region manager
> in the persistence manager layer
--
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
