You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2013/01/03 06:38:13 UTC

[jira] [Updated] (BOOKKEEPER-529) stopServingSubscriber in delivery manager should remove stub callbacks in ReadAheadCache

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

Sijie Guo updated BOOKKEEPER-529:
---------------------------------

    Attachment: BOOKKEEPER-529.diff
    
> stopServingSubscriber in delivery manager should remove stub callbacks in ReadAheadCache
> ----------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-529
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-529
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: hedwig-server
>            Reporter: Sijie Guo
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-529.diff
>
>
> Currently each subscriber would insert stub callback to wait newly published messages or scanning result. for waiting scan result, it was OK. the callback would be triggered and removed after scan callback arrived. but if it was wait newly published, it would be a problem. if sub/closesub/sub become frequent, closesub doesn't remove the installed callback, so the stub callbacks are accumulated, which cause the memory increased, finally OOM.
> it would be better to remove its installed stub callback when closesub.

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