[
https://issues.apache.org/jira/browse/BOOKKEEPER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212601#comment-13212601
]
Sijie Guo commented on BOOKKEEPER-168:
--------------------------------------
the new patch is well done, although I have two small problems to discuss as
below:
1) how we define the message bound? suppose I set the bound to 5, does it means
that subscriber would received latest 5 messages or 6 messages. currently the
subscriber can receive 6 messages. (you compute minSeqId by lastPushedSeqId -
messageBound)
2) is it possible to expose message bound as a parameter to override a
configuration setting? or provide a more general subscribe api to pass
subscription specified parameters like a key/value map.
#subscribe(topic, subscribe, parameters /*a key/value map*/)
> 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
>
>
> 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
