[jira] [Updated] (BOOKKEEPER-506) Provide better topic release algorithm

["Sijie Guo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo updated BOOKKEEPER-506:
---------------------------------

    Attachment: BOOKKEEPER-506.diff

a straightforward change to using guava cache to store its owned topics and track its accesses (publish a new message, deliver messages).

release topic when a entry is evicted from the cache. one is based on size (the owned topic reached the limitation that a hub server is supposed to own), the other one is based on 'expireAfterAccess', if a topic is inactive for a duration, the topic would be evicted and released.

'expireAfterAccess' is better than fixed time retention, so we don't release hot topics.
                
> Provide better topic release algorithm
> --------------------------------------
>
>                 Key: BOOKKEEPER-506
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-506
>             Project: Bookkeeper
>          Issue Type: Sub-task
>            Reporter: Sijie Guo
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-506.diff
>
>
> Currently time-based topic ownership release algorithm doesn't work well. A better algorithm is to release based on its traffic and the total memory usage by hub server.

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