-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Http2Session maximum invalid frame count configurable #30505
Labels
discuss
Issues opened for discussions and feedbacks.
feature request
Issues that request new features to be added to Node.js.
http2
Issues or PRs related to the http2 subsystem.
Comments
lundibundi
added
discuss
Issues opened for discussions and feedbacks.
feature request
Issues that request new features to be added to Node.js.
http2
Issues or PRs related to the http2 subsystem.
labels
Nov 16, 2019
@lundibundi I think using |
4 tasks
addaleax
pushed a commit
that referenced
this issue
Nov 27, 2019
* use new maxSessionInvalidFrames to lower the needed frames * slow down requests to generate less redundant after-session-close requests PR-URL: #30534 Fixes: #30505 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
addaleax
pushed a commit
that referenced
this issue
Nov 30, 2019
* use new maxSessionInvalidFrames to lower the needed frames * slow down requests to generate less redundant after-session-close requests PR-URL: #30534 Fixes: #30505 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
targos
pushed a commit
that referenced
this issue
Jan 13, 2020
* use new maxSessionInvalidFrames to lower the needed frames * slow down requests to generate less redundant after-session-close requests PR-URL: #30534 Fixes: #30505 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
BethGriggs
pushed a commit
that referenced
this issue
Feb 6, 2020
* use new maxSessionInvalidFrames to lower the needed frames * slow down requests to generate less redundant after-session-close requests PR-URL: #30534 Fixes: #30505 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: David Carlier <devnexen@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
discuss
Issues opened for discussions and feedbacks.
feature request
Issues that request new features to be added to Node.js.
http2
Issues or PRs related to the http2 subsystem.
Is your feature request related to a problem? Please describe.
We have flaky #29802 that doesn't hit the needed amount of invalid frames and crashes with OOM which may be solved by decreasing the amount of maximum invalid frames for that test.
It may prove useful for people to be able to configure how many invalid frames they want to tolerate though I don't think it'll be a popular feature.
At the same time, it shouldn't add too much of a maintenance burden to us.
Describe the solution you'd like
Probably option of
maxSessionInvalidFrames
(comepletely open to better names) tohttp2.createServer()
/http2.createSecureServer()
and possiblyhttp2.connect()
. I don't think this needs to be changed on the go and can be set upon server creation, though dynamic change may be useful.Though I'm not sure how to pass that to our C++-land
Http2Session
? (viajs_fields_
; property on Http2Session accessible from JS; constructor param?)Describe alternatives you've considered
None probably, it's hardcoded so it can stay that way.
/cc @addaleax as the one who added invalid frame counting.
/cc @nodejs/http2
The text was updated successfully, but these errors were encountered: