[
https://issues.apache.org/jira/browse/BOOKKEEPER-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sijie Guo updated BOOKKEEPER-367:
---------------------------------
Attachment: BOOKKEEPER-367.diff
attach a patch to enable server-side delivery throttle, which is required for
multiplexing.
the fix is quite straightforward, which checks the gap between
lastConsumedSeqId and lastDeliveredSeqId, whether it is over the throttle
value. we stopped the delivery process until receiving new consume request
which moves the consume ptr. If the gap reduced, we added the active subscriber
to the delivery queue to deliver the message again.
the patch is generated based on BOOKKEEPER-364.
> Server-Side Message Delivery Flow Control
> -----------------------------------------
>
> Key: BOOKKEEPER-367
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-367
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-367.diff
>
>
> Currently the message delivery flow control is proceed in client side. For
> multiplexing, we had to move the flow control to sever side.
--
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
