[
https://issues.apache.org/jira/browse/TS-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151961#comment-15151961
]
ASF GitHub Bot commented on TS-4087:
------------------------------------
GitHub user masaori335 opened a pull request:
https://github.com/apache/trafficserver/pull/485
TS-4087: Reduce SETTINGS_MAX_CONCURRENT_STREAMS when too many streams
Add below variables in records.config
- proxy.config.http2.min_concurrent_streams_in
- proxy.config.http2.max_active_streams_in
When connection wide active streams are larger than
proxy.config.http2.max_active_streams_in,
SETTINGS_MAX_CONCURRENT_STREAMS is reduced to
proxy.config.http2.min_concurrent_streams_in.
[TS-4087](https://issues.apache.org/jira/browse/TS-4087)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/masaori335/trafficserver ts-4087
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/485.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #485
----
commit ed7552d78ed12ec42b8ac95ffdcf2b0932691211
Author: Masaori Koshiba <[email protected]>
Date: 2016-02-15T11:57:25Z
TS-4087: Reduce SETTINGS_MAX_CONCURRENT_STREAMS when too many streams
Add below variables in records.config
- proxy.config.http2.min_concurrent_streams_in
- proxy.config.http2.max_active_streams_in
When connection wide active streams are larger than
proxy.config.http2.max_active_streams_in,
SETTINGS_MAX_CONCURRENT_STREAMS is reduced to
proxy.config.http2.min_concurrent_streams_in.
----
> H2 flexible resource limitation
> -------------------------------
>
> Key: TS-4087
> URL: https://issues.apache.org/jira/browse/TS-4087
> Project: Traffic Server
> Issue Type: New Feature
> Components: HTTP/2
> Reporter: Ryo Okubo
> Assignee: Masaori Koshiba
> Fix For: 6.2.0
>
>
> Current H2 implementation depends on FetchSM and PluginVC to forward
> requests. But their memory footprint is very high. It may be vulnerable to
> DoS attack.
> As simple ways to avoid the problem, we can use two limitations,
> _proxy.config.net.connections_throttle_ and
> _proxy.config.http2.max_concurrent_streams_in_. But reducing number of
> _proxy.config.net.connections_throttle_ causes that number of acceptable
> HTTP/1.1 requests become lower. And reducing
> _proxy.config.http2.max_concurrent_streams_in_ restricts benefits of H2.
> I'd like to propose more flexible resource limitation for current H2 impl
> based on number of active H2 streams. Its adding an upper limit of active H2
> streams. If tis exceeded, ATS send low number of
> SETTINGS_MAX_CONCURRENT_STREAMS to clients and/or RST_STREAM frame.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
