[
https://issues.apache.org/jira/browse/BOOKKEEPER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229122#comment-13229122
]
Ivan Kelly commented on BOOKKEEPER-168:
---------------------------------------
It is a valid scenario, but it belongs in another JIRA. The current fix
addresses the requirement and usecases we currently have. If in the future we
find ourselves with a usecase which requires time based bounding, we can add it
then.
> Message bounding on subscriptions
> ---------------------------------
>
> Key: BOOKKEEPER-168
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-168
> Project: Bookkeeper
> Issue Type: New Feature
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.1.0
>
> Attachments: BOOKKEEPER-168.diff, BOOKKEEPER-168.diff,
> BOOKKEEPER-168.diff
>
>
> In hedwig, messages for a subscription will queue up forever if the
> subscriber is offline. In some usecases, this is undesirable, as it will
> eventually mean resource exhaustion. In this JIRA we propose an optional
> change to the subscription contract, which allows the user to set a bound on
> the number of messages which will be queued for its subscription while it is
> offline.
--
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
