Igor Canadi
758fa8c359
Don't Finalize in CompactionPicker
Summary: Finalize re-sorts (read: mutates) the files_ in Version* and it is called by CompactionPicker during normal runtime. At the same time, this same Version* lives in the SuperVersion* and is accessed without the mutex in GetImpl() code path. Mutating the files_ in one thread and reading the same files_ in another thread is a bad idea. It caused this issue: http://ci-builds.fb.com/job/rocksdb_crashtest/285/console Long-term, we need to be more careful with method contracts and clearly document what state can be mutated when. Now that we are much faster because we don't lock in GetImpl(), we keep running into data races that were not a problem before when we were slower. db_stress has been very helpful in detecting those. Short-term, I removed Finalize() from CompactionPicker. Note: I believe this is an issue in current 2.7 version running in production. Test Plan: make check Will also run db_stress to see if issue is gone Reviewers: sdong, ljin, dhruba, haobo Reviewed By: sdong CC: leveldb Differential Revision: https://reviews.facebook.net/D16983
rocksdb: A persistent key-value store for flash storage Authors: * The Facebook Database Engineering Team * Build on earlier work on leveldb by Sanjay Ghemawat (sanjay@google.com) and Jeff Dean (jeff@google.com) This code is a library that forms the core building block for a fast key value server, especially suited for storing data on flash drives. It has an Log-Structured-Merge-Database (LSM) design with flexible tradeoffs between Write-Amplification-Factor(WAF), Read-Amplification-Factor (RAF) and Space-Amplification-Factor(SAF). It has multi-threaded compactions, making it specially suitable for storing multiple terabytes of data in a single database. The core of this code has been derived from open-source leveldb. The code under this directory implements a system for maintaining a persistent key/value store. See doc/index.html and github wiki (https://github.com/facebook/rocksdb/wiki) for more explanation. The public interface is in include/*. Callers should not include or rely on the details of any other header files in this package. Those internal APIs may be changed without warning. Guide to header files: include/rocksdb/db.h Main interface to the DB: Start here include/rocksdb/options.h Control over the behavior of an entire database, and also control over the behavior of individual reads and writes. include/rocksdb/comparator.h Abstraction for user-specified comparison function. If you want just bytewise comparison of keys, you can use the default comparator, but clients can write their own comparator implementations if they want custom ordering (e.g. to handle different character encodings, etc.) include/rocksdb/iterator.h Interface for iterating over data. You can get an iterator from a DB object. include/rocksdb/write_batch.h Interface for atomically applying multiple updates to a database. include/rocksdb/slice.h A simple module for maintaining a pointer and a length into some other byte array. include/rocksdb/status.h Status is returned from many of the public interfaces and is used to report success and various kinds of errors. include/rocksdb/env.h Abstraction of the OS environment. A posix implementation of this interface is in util/env_posix.cc include/rocksdb/table_builder.h Lower-level modules that most clients probably won't use directly include/rocksdb/cache.h An API for the block cache. include/rocksdb/compaction_filter.h An API for a application filter invoked on every compaction. include/rocksdb/filter_policy.h An API for configuring a bloom filter. include/rocksdb/memtablerep.h An API for implementing a memtable. include/rocksdb/statistics.h An API to retrieve various database statistics. include/rocksdb/transaction_log.h An API to retrieve transaction logs from a database. Design discussions are conducted in https://www.facebook.com/groups/rocksdb.dev/
Description
Languages
C++
82.1%
Java
10.3%
C
2.5%
Python
1.7%
Perl
1.1%
Other
2.1%