You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ganesh Murthy (Jira)" <ji...@apache.org> on 2021/11/02 19:33:00 UTC
[jira] [Updated] (DISPATCH-2007) Need better allocation of sessions
across inter-router links
[ https://issues.apache.org/jira/browse/DISPATCH-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ganesh Murthy updated DISPATCH-2007:
------------------------------------
Fix Version/s: (was: 1.18.0)
1.19.0
> Need better allocation of sessions across inter-router links
> ------------------------------------------------------------
>
> Key: DISPATCH-2007
> URL: https://issues.apache.org/jira/browse/DISPATCH-2007
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 1.15.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Fix For: 1.19.0
>
>
> Inter-router connections establish several links for passing traffic between routers. Session allocation across the links is currently:
> * one session dedicated to both router control links
> * one session for EACH priority link pair (in/out) - 10 sessions total
> * one session used by all link route links
> * one session used by all streaming link
> There is an issue with sharing the session in the case of streaming & link routes. Due to the way session flow control works all links on the session share bandwidth. This means one slow link can force flow control on all of its peer links on the session.
> Proton allows for at most 32K sessions per connection. We should make an attempt to use dedicated sessions for link route and streaming links, sharing only when the number of link route + streaming links exceeds the proton limit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org