-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
ThreadSanitizer: use of an invalid mutex (e.g. uninitialized or destroyed) (pid=7) #3279
Closed
6 of 7 tasks
Comments
filimonov
added a commit
to ClickHouse/ClickHouse
that referenced
this issue
Mar 4, 2021
Extra info: |
edenhill
added a commit
that referenced
this issue
Mar 8, 2021
As ops on broker queues may have references to the metadata cache's mutex
edenhill
added a commit
that referenced
this issue
Mar 8, 2021
As ops on broker queues may have references to the metadata cache's mutex
Fixed on master |
azat
added a commit
to azat/ClickHouse
that referenced
this issue
Aug 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
ThreadSanitizer in ClickHouse CI catched 'use of an invalid mutex'
https://clickhouse-test-reports.s3.yandex.net/0/174f49a9f13f87e3ad326043c249dad06e9b0e9b/integration_tests_(thread).html#fail1
How to reproduce
Scenario like following
It seems the failure happened on p.2.
Thread sanitizer report:
Log fragment before failure:
Checklist
v1.6.0
5.2.0
auto.offset.reset=earliest; debug=cgrp,consumer,topic,protocol,metadata; broker.list=kafka1:19092; client.software.name=ClickHouse; client.software.version=v21.3.1.1-prestable; queued.min.messages=1048545; enable.auto.commit=false; enable.auto.offset.store=false; enable.partition.eof=false; client.id="ClickHouse-instance-test-kafka_q"
Ubuntu:20.04
debug=..
as necessary) from librdkafka - see aboveThe text was updated successfully, but these errors were encountered: