Skip to content
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

Support full configuration of TCP keepalive probles, upgrading to v3.0.0 #7

Merged
merged 1 commit into from
Sep 30, 2022
Merged

Conversation

hansonchar
Copy link

@hansonchar hansonchar commented Sep 30, 2022

Issue #, if available:

Description of changes:

aws-kms-xks-proxy currently depends on two crates to enable TCP keep-alive, axum-server and hyper which axum-server depends upon. However, both crates need to be fixed in terms of supporting TCP keep-alive retries and retry intervals. The pull request to hyper has been accepted upstream to branch 0.14.x, but the ETA of release is currently unknown.

This pull request is to support full configuration of TCP keep-alive probes. In doing so, it

  1. changes hyper to depend on the tip of branch 0.14.x; and
  2. makes a local copy of axum-server v0.4.2 and applys local patches to allow the configuration of all the TCP keep-alive parameters.

Without this change, a busy server can easily run out of file descriptors if TCP keepalive is disabled, or end up having unstable persistent TCP connections (due to false positives of detecting dead connections) when TCP keepalive is enabled.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Use hyper stream branch 0.14.x

Locally patched axum-server to make all TCP keepalive parameters available

  ref: git@github.com:hansonchar/axum-server.git
  branch: v0.4.3
  commit: 839ada3

#7
@hansonchar hansonchar merged commit 63c6d28 into aws-samples:main Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants