mirror of
https://github.com/ClickHouse/ClickHouse.git
synced 2024-12-11 00:42:29 +00:00
5a4f21c50f
- TSA is a static analyzer build by Google which finds race conditions
and deadlocks at compile time.
- It works by associating a shared member variable with a
synchronization primitive that protects it. The compiler can then
check at each access if proper locking happened before. A good
introduction are [0] and [1].
- TSA requires some help by the programmer via annotations. Luckily,
LLVM's libcxx already has annotations for std::mutex, std::lock_guard,
std::shared_mutex and std::scoped_lock. This commit enables them
(--> contrib/libcxx-cmake/CMakeLists.txt).
- Further, this commit adds convenience macros for the low-level
annotations for use in ClickHouse (--> base/defines.h). For
demonstration, they are leveraged in a few places.
- As we compile with "-Wall -Wextra -Weverything", the required compiler
flag "-Wthread-safety-analysis" was already enabled. Negative checks
are an experimental feature of TSA and disabled
(--> cmake/warnings.cmake). Compile times did not increase noticeably.
- TSA is used in a few places with simple locking. I tried TSA also
where locking is more complex. The problem was usually that it is
unclear which data is protected by which lock :-(. But there was
definitely some weird code where locking looked broken. So there is
some potential to find bugs.
*** Limitations of TSA besides the ones listed in [1]:
- The programmer needs to know which lock protects which piece of shared
data. This is not always easy for large classes.
- Two synchronization primitives used in ClickHouse are not annotated in
libcxx:
(1) std::unique_lock: A releaseable lock handle often together with
std::condition_variable, e.g. in solve producer-consumer problems.
(2) std::recursive_mutex: A re-entrant mutex variant. Its usage can be
considered a design flaw + typically it is slower than a standard
mutex. In this commit, one std::recursive_mutex was converted to
std::mutex and annotated with TSA.
- For free-standing functions (e.g. helper functions) which are passed
shared data members, it can be tricky to specify the associated lock.
This is because the annotations use the normal C++ rules for symbol
resolution.
[0] https://clang.llvm.org/docs/ThreadSafetyAnalysis.html
[1] https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/42958.pdf
49 lines
1.2 KiB
C++
49 lines
1.2 KiB
C++
#pragma once
|
|
|
|
#include <atomic>
|
|
#include <map>
|
|
#include <mutex>
|
|
#include <Core/Types.h>
|
|
#include <base/defines.h>
|
|
#include <libnuraft/log_store.hxx>
|
|
|
|
namespace DB
|
|
{
|
|
|
|
class InMemoryLogStore : public nuraft::log_store
|
|
{
|
|
public:
|
|
InMemoryLogStore();
|
|
|
|
uint64_t start_index() const override;
|
|
|
|
uint64_t next_slot() const override;
|
|
|
|
nuraft::ptr<nuraft::log_entry> last_entry() const override;
|
|
|
|
uint64_t append(nuraft::ptr<nuraft::log_entry> & entry) override;
|
|
|
|
void write_at(uint64_t index, nuraft::ptr<nuraft::log_entry> & entry) override;
|
|
|
|
nuraft::ptr<std::vector<nuraft::ptr<nuraft::log_entry>>> log_entries(uint64_t start, uint64_t end) override;
|
|
|
|
nuraft::ptr<nuraft::log_entry> entry_at(uint64_t index) override;
|
|
|
|
uint64_t term_at(uint64_t index) override;
|
|
|
|
nuraft::ptr<nuraft::buffer> pack(uint64_t index, Int32 cnt) override;
|
|
|
|
void apply_pack(uint64_t index, nuraft::buffer & pack) override;
|
|
|
|
bool compact(uint64_t last_log_index) override;
|
|
|
|
bool flush() override { return true; }
|
|
|
|
private:
|
|
std::map<uint64_t, nuraft::ptr<nuraft::log_entry>> logs TSA_GUARDED_BY(logs_lock);
|
|
mutable std::mutex logs_lock;
|
|
std::atomic<uint64_t> start_idx;
|
|
};
|
|
|
|
}
|