We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes we may want to configure the TCP keepalive idle for a connection in the Postgres or MySQL handler of GreptimeDB
https://www.postgresql.org/docs/current/runtime-config-connection.html#RUNTIME-CONFIG-TCP-SETTINGS
It may be useful if we run the fronted after an LB so we can use the keepalive probe to keep the connection.
What's more, we may also find a way to configure the keepalive idle for the HTTP server since we can't set that in axum after #5417
Adds server side configurations for keepalive related options
We have the following different handlers to support
It isn't easy to test in an integration test.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What problem does the new feature solve?
Sometimes we may want to configure the TCP keepalive idle for a connection in the Postgres or MySQL handler of GreptimeDB
https://www.postgresql.org/docs/current/runtime-config-connection.html#RUNTIME-CONFIG-TCP-SETTINGS
It may be useful if we run the fronted after an LB so we can use the keepalive probe to keep the connection.
What's more, we may also find a way to configure the keepalive idle for the HTTP server since we can't set that in axum after #5417
What does the feature do?
Adds server side configurations for keepalive related options
Implementation challenges
We have the following different handlers to support
It isn't easy to test in an integration test.
The text was updated successfully, but these errors were encountered: