Revision 4e0dcd36dfcf3109c4a8ede9c793bc8b1f76e68b authored by sdong on 19 November 2019, 21:15:40 UTC, committed by Facebook Github Bot on 19 November 2019, 21:17:03 UTC
Summary:
Recently, a bug was found related to a seek key that is close to SST file boundary. However, it only occurs in a very small chance in db_stress, because the chance that a random key hits SST file boundaries is small. To boost the chance, with 1/16 chance, we pick keys that are close to SST file boundaries.
Pull Request resolved: https://github.com/facebook/rocksdb/pull/6037

Test Plan: Did some manual printing out, and hack to cover the key generation logic to be correct.

Differential Revision: D18598476

fbshipit-source-id: 13b76687d106c5be4e3e02a0c77fa5578105a071
1 parent 20b48c6
History
File Mode Size
env.cc -rw-r--r-- 13.5 KB
env_basic_test.cc -rw-r--r-- 12.6 KB
env_chroot.cc -rw-r--r-- 11.6 KB
env_chroot.h -rw-r--r-- 684 bytes
env_encryption.cc -rw-r--r-- 33.9 KB
env_hdfs.cc -rw-r--r-- 19.2 KB
env_posix.cc -rw-r--r-- 37.4 KB
env_test.cc -rw-r--r-- 57.4 KB
io_posix.cc -rw-r--r-- 33.0 KB
io_posix.h -rw-r--r-- 8.7 KB
mock_env.cc -rw-r--r-- 20.7 KB
mock_env.h -rw-r--r-- 4.2 KB
mock_env_test.cc -rw-r--r-- 2.7 KB

back to top