Try to reconnect right after connection is closed (FIN arrived) instead of on query or ping #210
Assignees
Comments
ananthakumaran
added a commit
to ananthakumaran/ch
that referenced
this issue
Nov 9, 2024
A server may return `Connection: close` while gracefully shutting down. Mint will mark the connection state as closed and return the response from the server (NOTE: it will not return any error). Since the client doesn't know the connection is closed, it will try to use the connection for the next request and will fail. Before making any HTTP request, check the internal state of the connection and attempt to reconnect once if necessary. partially related to plausible#210
ruslandoga
pushed a commit
that referenced
this issue
Nov 9, 2024
A server may return `Connection: close` while gracefully shutting down. Mint will mark the connection state as closed and return the response from the server (NOTE: it will not return any error). Since the client doesn't know the connection is closed, it will try to use the connection for the next request and will fail. Before making any HTTP request, check the internal state of the connection and attempt to reconnect once if necessary. partially related to #210
This was referenced Nov 9, 2024
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context: #208
Possible solutions:
active socketsretry queries on error=closedThe text was updated successfully, but these errors were encountered: