You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2019/06/10 18:07:00 UTC
[jira] [Created] (DISPATCH-1360) forward pre-settled messages as
unsettled within the dispatch network
Ken Giusti created DISPATCH-1360:
------------------------------------
Summary: forward pre-settled messages as unsettled within the dispatch network
Key: DISPATCH-1360
URL: https://issues.apache.org/jira/browse/DISPATCH-1360
Project: Qpid Dispatch
Issue Type: Improvement
Components: Router Node
Affects Versions: 1.8.0
Reporter: Ken Giusti
Fix For: 1.9.0
Possible approach to credit replenishment for pre-settled messages.
For unsettled messages the router correlates the eventual settlement of the message with credit flow to the sender. This provides a reasonable method for rate limiting the sender.
However this approach does not apply to pre-settled messages. For these the router simply grants sender credit when the message is forwarded, which tends to over-provisioning credit.
Let's try to apply the behavior of the unsettled case to the settled by forwarding presettled messages as unsettled between routers. It would work something like this:
* presettled msg arrrives at ingress router - no flow granted
* ingress router adds a "presettled" flag to the annotations and forwards the message into the routing network as unsettled.
* at the egress router if the "presettled" flag is in the annotations the message is forwarded to the receiver as presettled.
* the egress router generates an PN_ACCEPTED/Settled event for the message
* which travels back to the ingress router which uses that event to grant flow to the sender.
de[devil]tails, etc...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org