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

Posted to dev@bookkeeper.apache.org by "Yixue (Andrew) Zhu (JIRA)" <ji...@apache.org> on 2012/10/24 18:42:11 UTC

[jira] [Updated] (BOOKKEEPER-441) InMemorySubscriptionManager should back up top2sub2seq before change it

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

Yixue (Andrew) Zhu updated BOOKKEEPER-441:
------------------------------------------

    Labels: patch  (was: )
    
> InMemorySubscriptionManager should back up top2sub2seq before change it
> -----------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-441
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-441
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>    Affects Versions: 4.3.0
>         Environment: unix
>            Reporter: Yixue (Andrew) Zhu
>            Priority: Minor
>              Labels: patch
>             Fix For: 4.3.0
>
>
> On topic loss, InMemorySubscriptionManager currently does not clear top2sub2seq. The intent is to allow readSubscription to get the information there. This introduce dependency outside the class, evidence is that general ReleaseOp has to use a boolean parameter which targets this implementation detail. Further, this prevents Acquire-topic to notify listeners (notifyFirstLocalSubscribe is not called) of first subscription to act appropriately.

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