[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185732#comment-13185732
 ] 

Daniel Kim commented on BOOKKEEPER-151:
---------------------------------------

Yes, it seems like eager delete may break some guarantee. I would like to see 
it someday when we are capable of adding the eager delete function in there, 
however, I coded around the issue for now. I use Zookeeper client to set a flag 
in the hedwig/standalone/topics/myTopic/deleted znode and my application just 
checks it. This approach is working well enough for now, so I'll live with it. 
Thank you for your concern.
                
> 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

        

Reply via email to