-
Notifications
You must be signed in to change notification settings - Fork 64
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
feat(backend): Support configuring connection keepalive parameters #1275
Conversation
d48cdd9
to
b1ef3a5
Compare
This will depend on pulling in fastly/go-fastly#537 once it has a tag we can put in |
@kpfleming this PR requires a new go-fastly release that contains fastly/go-fastly#537 |
This will need tests added in |
The build is failing...
|
I haven't made a go-fastly release yet, so unless someone else did this will continue. That's on my agenda for today if nobody else does it first. |
go-fastly 9.8.0 has been released. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very very close :-)
This is a draft PR that adds support for creating and updating backends with the different keepalive parameters:
keepalive_time
, which is how long HTTP keepalive connections will be kept when they are idle; I've made the flag for this--http-ka-time
to make it easier to differentiate with the--tcp-ka-*
flags.tcp_keepalive_enable
, which determines whether TCP keepalives are turned on on connections.tcp_keepalive_interval
which determines how long to wait in between sending each TCP keepalive probe.tcp_keepalive_probes
which determines up to how many probes to send before considering the connection dead.tcp_keepalive_time
which determines how long to wait after sending the last data packet before starting to send TCP keepalive probes.