You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Gavin Li (Commented) (JIRA)" <ji...@apache.org> on 2012/02/01 08:30:58 UTC

[jira] [Commented] (BOOKKEEPER-154) Garbage collect messages for those subscribers inactive/offline for a long time.

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

Gavin Li commented on BOOKKEEPER-154:
-------------------------------------

To recycle the old enough messages is the ideal case we want to achieve. But it seems very complicated to implement and takes too long. Maybe we can't wait for that. What is actually enough for us is to consume all the old message for users that being inactive for long enough time. How long the user has been inactive can be specified as a parameter.

Actually in this way we can have kind of size based recycle. The SE can firstly specify a large enough inactive time, say 20 days. Then it can recycle some space. If it's not enough, SE can run once more with smaller time to free up more space.

 
                
> Garbage collect messages for those subscribers inactive/offline for a long time. 
> ---------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-154
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-154
>             Project: Bookkeeper
>          Issue Type: New Feature
>          Components: hedwig-client, hedwig-server
>    Affects Versions: 4.0.0
>            Reporter: Sijie Guo
>
> Currently hedwig tracks subscribers progress for garbage collecting published messages. If subscriber subscribe and becomes offline without unsubscribing for a long time, those messages published in its topic have no chance to be garbage collected.
> A time based garbage collection policy would be suitable for this case. 

--
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