[
https://issues.apache.org/jira/browse/BOOKKEEPER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185718#comment-13185718
]
Flavio Junqueira commented on BOOKKEEPER-151:
---------------------------------------------
Hi Daniel, You're saying that the lazy cleanup is not the right way for you?
I'm bit concerned about having an eager delete call, since it might affect our
guarantees to subscribers. In general, if there is a subscriber still
subscriber, then we should be able to guarantee that the subscriber will
receive published messages. If we have an eager delete, then we won't be able
to fulfill that guarantee in the case we delete the topic and all related data.
> Delete method for Hedwig client API that uses eager cleanup
> -----------------------------------------------------------
>
> Key: BOOKKEEPER-151
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-151
> Project: Bookkeeper
> Issue Type: Wish
> Components: hedwig-client, hedwig-server
> Environment: Ubuntu / Centos
> Reporter: Daniel Kim
> Labels: features, new
>
> I am using hedwig as a notification system for my webapp. However, the
> current version of hedwig does not have any api for deleting topics. Since I
> want to be able to manage the resources, I tried to "delete" a topic by
> removing the znodes associated with the topic. However, the hubs do not lose
> their ownership of their delete topics until the redistribution period (e.g.,
> lazy cleanup). The hubs will behave as if they still own the topic, which has
> no information in zookeeper server(s). I am hoping to see a hedwig-client api
> that does eager delete.
> As of now, the system is unthrottled and thus can grow without bound. This
> poses a threat where my resources can run out by malicious use cases, rogue
> programmers, etc.
--
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
