Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

CI: Data race when executing ScyllaDB interface #286

Open
YingHan-Chen opened this issue Aug 26, 2019 · 2 comments
Open

CI: Data race when executing ScyllaDB interface #286

YingHan-Chen opened this issue Aug 26, 2019 · 2 comments
Labels
A-storage Area - Storage A-tests Area - Tests C-bug Category - Something isn't working P-medium Priority - Medium, not hurry but needed

Comments

@YingHan-Chen
Copy link
Contributor

Description

Running CI in node1, the test_scylla will connect to Scylla node in node0.
However, there are many data races happened.

Below is part of the test log.
`==================
WARNING: ThreadSanitizer: data race (pid=14)
Read of size 1 at 0x7b2c0007ff64 by thread T6:
#0 writev (libtsan.so.0+0x33cba)
#1 (libuv.so.1+0x15a7a)

Previous write of size 8 at 0x7b2c0007ff60 by main thread:
#0 malloc (libtsan.so.0+0x2ae03)
#1 datastax::internal::core::Buffer::Buffer(unsigned long) (libcassandra.so.2+0x9ac24)
#2 create_bundle_table storage/scylla_api.c:190 (libstorage_Slibstorage.so+0x299d)
#3 init_scylla storage/scylla_api.c:248 (libstorage_Slibstorage.so+0x2b35)
#4 main tests/test_scylla.c:134 (test_scylla+0x2a77)

Location is heap block of size 170 at 0x7b2c0007ff60 allocated by main thread:
#0 malloc (libtsan.so.0+0x2ae03)
#1 datastax::internal::core::Buffer::Buffer(unsigned long) (libcassandra.so.2+0x9ac24)
#2 create_bundle_table storage/scylla_api.c:190 (libstorage_Slibstorage.so+0x299d)
#3 init_scylla storage/scylla_api.c:248 (libstorage_Slibstorage.so+0x2b35)
#4 main tests/test_scylla.c:134 (test_scylla+0x2a77)

Thread T6 (tid=21, running) created by thread T1 at:
#0 pthread_create (libtsan.so.0+0x2bcee)
#1 uv_thread_create (libuv.so.1+0x17cc0)

SUMMARY: ThreadSanitizer: data race (/usr/lib/x86_64-linux-gnu/libtsan.so.0+0x33cba) in writev

==================
WARNING: ThreadSanitizer: data race (pid=14)
Atomic read of size 1 at 0x7b3800000010 by thread T6:
#0 pthread_mutex_lock (libtsan.so.0+0x3fadb)
#1 uv_mutex_lock (libuv.so.1+0x17e18)

Previous write of size 8 at 0x7b3800000010 by main thread:
#0 malloc (libtsan.so.0+0x2ae03)
#1 datastax::internal::core::Session::execute(datastax::internal::SharedRefPtr<datastax::internal::core::Request const> const&, datastax::internal::core::Address const*) (libcassandra.so.2+0x182663)
#2 create_bundle_table storage/scylla_api.c:190 (libstorage_Slibstorage.so+0x299d)
#3 init_scylla storage/scylla_api.c:248 (libstorage_Slibstorage.so+0x2b35)
#4 main tests/test_scylla.c:134 (test_scylla+0x2a77)

Location is heap block of size 224 at 0x7b3800000000 allocated by main thread:
#0 malloc (libtsan.so.0+0x2ae03)
#1 datastax::internal::core::Session::execute(datastax::internal::SharedRefPtr<datastax::internal::core::Request const> const&, datastax::internal::core::Address const*) (libcassandra.so.2+0x182663)
#2 create_bundle_table storage/scylla_api.c:190 (libstorage_Slibstorage.so+0x299d)
#3 init_scylla storage/scylla_api.c:248 (libstorage_Slibstorage.so+0x2b35)
#4 main tests/test_scylla.c:134 (test_scylla+0x2a77)

Thread T6 (tid=21, running) created by thread T1 at:
#0 pthread_create (libtsan.so.0+0x2bcee)
#1 uv_thread_create (libuv.so.1+0x17cc0)

SUMMARY: ThreadSanitizer: data race (/usr/lib/x86_64-linux-gnu/libtsan.so.0+0x3fadb) in __interceptor_pthread_mutex_lock

`

@howjmay howjmay added A-storage Area - Storage A-tests Area - Tests C-bug Category - Something isn't working P-high Priority - High, important issues or features labels Jan 5, 2020
@howjmay
Copy link
Contributor

howjmay commented Jan 5, 2020

@locke2833 Have we got any progress on this issue?

@howjmay howjmay added P-medium Priority - Medium, not hurry but needed and removed P-high Priority - High, important issues or features labels Jan 5, 2020
@jserv jserv changed the title Data race when run CI for Scylla interface Jan 6, 2020
@jserv jserv changed the title CI: Data race when executing Scylla interface Jan 6, 2020
@howjmay
Copy link
Contributor

howjmay commented Feb 26, 2020

@YingHan-Chen We have implemented keyspace name assigning in scyllaDB interface, so can we close this issue?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-storage Area - Storage A-tests Area - Tests C-bug Category - Something isn't working P-medium Priority - Medium, not hurry but needed
2 participants