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
lock-order-inversion in RemoteQueryExecutor::sendQuery #48534
Comments
cc @Avogar |
Hmm. I don't understand. As I can see from the first stacktrace, M1 is located in |
It can be a result of a memory safety issue. For example, we tried to lock a mutex that was already destroyed. |
Also Nikolai mentioned interesting thing, both stacktraces have the same thread T563 |
Probably it's from test |
…plication=1) It looks redundant, since sendQuery() cannot be executed in parallel with processPacket() (hence RemoteQueryExecutor::setPartUUIDs()) This likely will fix the lock-order-inversion in RemoteQueryExecutor, since I think it is false-positive. Fixes: ClickHouse#48534 Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
I think that this one is false-positive, maybe google/sanitizers#814 looks similar. But actually looking into this code, I don't see that Other thing that I have in mind is that But, even better will be to remove |
https://s3.amazonaws.com/clickhouse-test-reports/48311/2d335f82cc8ea3dc18f6d05778de1b19c63aec01/stateless_tests__tsan__[3/5]/stderr.log
The text was updated successfully, but these errors were encountered: