[
https://issues.apache.org/jira/browse/BOOKKEEPER-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454096#comment-13454096
]
Aniruddha commented on BOOKKEEPER-402:
--------------------------------------
Sorry about the missing reviewboard entry. For some reason I wasn't able to
update the jira yesterday night.
I glanced over BOOKKEEPER-252 and I believe it deals with letting the client's
application know about channel failures. But we want to be able to use the
reconnection logic in our case. Also, I think that it's more appropriate to
stop delivery as a side-effect of a lost subscription and not of a lost topic.
We should stop delivery only after the subscription manager is notified of the
lost topic and will not accept any more subscriptions for that topic.
> Hedwig hub should close subscription channels on losing a topic
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-402
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-402
> Project: Bookkeeper
> Issue Type: Bug
> Components: hedwig-server
> Reporter: Aniruddha
>
> If a hub were to lose a topic, it doesn't stop delivery for that topic and
> keeps the subscription channels open. It should actively close it and stop
> delivery for all subscribers for that topic connected to it.
> Reviewboard entry: https://reviews.apache.org/r/7054/
--
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
