[
https://issues.apache.org/jira/browse/DISPATCH-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388842#comment-17388842
]
Ken Giusti commented on DISPATCH-781:
-------------------------------------
Set target release to 2.0 under the assumption that the feature requires
changes to the routing protocol (possible version bump).
Feel free to re-target if my assumption is incorrect, thanks.
> Tie end-to-end flow control of message-routed deliveries to outgoing capacity
> -----------------------------------------------------------------------------
>
> Key: DISPATCH-781
> URL: https://issues.apache.org/jira/browse/DISPATCH-781
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node, Routing Engine
> Reporter: Ted Ross
> Assignee: Ted Ross
> Priority: Major
> Fix For: 2.0.0
>
>
> This feature reverses the management of incoming credit for message-routed
> deliveries.
> The current mechanism is based on the the capacity of the incoming
> (sender-client) links. Each attached sender is given credit equal to the
> configured link capacity regardless of the capacity of outgoing
> (receiver-client) links for the same address. This means that even under
> congestion, a newly attached sender will get full capacity credit to send.
> The proposed mechanism is based not on incoming capacity but on outgoing
> capacity. In this case, the senders are provided a share of the total
> outgoing capacity for an address. As the number of incoming links (senders)
> for an address changes and the total capacity for outgoing links changes, the
> credit window of the senders shall be adjusted.
> The proposal is a heuristic approach. It does not revoke credit from senders
> (but will limit the number of credits that are replenished). It will also
> not deny credit if there are more incoming links than outgoing capacity.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
