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 2021/08/06 13:28:00 UTC
[jira] [Commented] (DISPATCH-2006) Set stricter default
maxSessionFrames to avoid router OOM under load
[ https://issues.apache.org/jira/browse/DISPATCH-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394760#comment-17394760 ]
Ken Giusti commented on DISPATCH-2006:
--------------------------------------
Will experiment on possible fixes. Setting release target to 2.0 under the current assumption this may require breaking changes.
> Set stricter default maxSessionFrames to avoid router OOM under load
> --------------------------------------------------------------------
>
> Key: DISPATCH-2006
> URL: https://issues.apache.org/jira/browse/DISPATCH-2006
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 1.15.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Fix For: 2.0.0
>
>
> By default, sessions created by the router have an essentially unlimited session window size. This can result in unconstrained growth of router heap memory during periods of high traffic congestion.
>
> The router needs to use reasonable session incoming window limits by default. It's likely that different type of connections - endpoints, inter-router, etc - should have different default window sizes. For example it's reasonable to provide a bigger window for inter-router links than simple endpoint connections.
--
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