-
Notifications
You must be signed in to change notification settings - Fork 9
Check multiplexed connection before usage #1102
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
Conversation
| state.connection = nullptr; | ||
| state.pool_entry = IConnectionPool::Entry(); | ||
| --active_connection_count; | ||
| if (current_connection == old_connection) |
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.
Is it Ok that we don't acquire cancel_mutex here?
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.
Yes, invalidateReplica is called under that mutex already, like in MultiplexedConnections::disconnect https://github.com/Altinity/ClickHouse/blob/antalya/src/Client/MultiplexedConnections.cpp#L239
|
@ianton-ru please provide a proper description WHY we need this change and/or reference to the bug that it fixes. Otherwise there is no way to perform a code review of proper quality |
Crush catched by @filimonov. |
Enmk
left a comment
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.
LGTM
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Check multiplexed connection before usage
Documentation entry for user-facing changes
...
CI/CD Options
Exclude tests:
Regression jobs to run: