Branch v2.x-AT #4603
Closed
Branch v2.x-AT #4603
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The SSL error queue wasn't cleanup after an SSL related error took place
in a backend connection. This would result in the propagation of the
error to other conns handled by the thread, which could result in:
- Incorrect destruction of connections in conn-pool.
- Invalid error propagation to clients.
This is a consequence of 'libmariadbclient' not performing a cleanup of
this queue by itself. The situation got mitigated since the library
**does** perform a cleanup of such queue during connect phase
('auth_caching_sha2_client|auth_sha256_client'), and ProxySQL does a
cleanup of this queue during frontend SSL traffic.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is v2.x at commit 01d1fc9 , plus branch v2.x-backend_conns_ssl_err_clear (PR #4602)