You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (Created) (JIRA)" <ji...@apache.org> on 2011/10/07 12:38:29 UTC
[jira] [Created] (BOOKKEEPER-75) Disowning a topic does not
terminate subscriptions
Disowning a topic does not terminate subscriptions
---------------------------------------------------
Key: BOOKKEEPER-75
URL: https://issues.apache.org/jira/browse/BOOKKEEPER-75
Project: Bookkeeper
Issue Type: Bug
Reporter: Ivan Kelly
When a topic is dropped by the owning hub (e.g. due to a regularly scheduled topic relinquishing), subscribers are not
notified. AbstractSubscriptionManager.lostTopic() simply removes the topic from the local table. This only prevents
the system from being able to update subscription states for that topic (on consume calls); subscribers remain
oblivious to this fact, as the failed attempts do not result in errors. ActiveSubscriptionStates furthermore remain
present in the FIFODeliveryManager.
Proposed fix: notify subscribers with an error message so that they know to resubscribe (with whoever the new topic
owner is).
--
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
[jira] [Resolved] (BOOKKEEPER-75) Disowning a topic does not
terminate subscriptions
Posted by "Sijie Guo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BOOKKEEPER-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sijie Guo resolved BOOKKEEPER-75.
---------------------------------
Resolution: Duplicate
This issue is similar as BOOKKEEPER-402 and already fixed in BOOKKEEPER-252.
> Disowning a topic does not terminate subscriptions
> ---------------------------------------------------
>
> Key: BOOKKEEPER-75
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-75
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
>
> When a topic is dropped by the owning hub (e.g. due to a regularly scheduled topic relinquishing), subscribers are not
> notified. AbstractSubscriptionManager.lostTopic() simply removes the topic from the local table. This only prevents
> the system from being able to update subscription states for that topic (on consume calls); subscribers remain
> oblivious to this fact, as the failed attempts do not result in errors. ActiveSubscriptionStates furthermore remain
> present in the FIFODeliveryManager.
> Proposed fix: notify subscribers with an error message so that they know to resubscribe (with whoever the new topic
> owner is).
--
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