]> git.apps.os.sepia.ceph.com Git - ceph.git/commit
kv: make delete range optional on number of keys 27317/head
authorZengran Zhang <zhangzengran@sangfor.com.cn>
Tue, 2 Apr 2019 14:03:45 +0000 (22:03 +0800)
committerZengran Zhang <zhangzengran@sangfor.com.cn>
Wed, 3 Apr 2019 08:47:36 +0000 (16:47 +0800)
commitb039e63c6816ed371c6db975b4cbc7a3d170bb1f
treed554692217c0fc918ebd0e536d24abbff361f688
parent33357740f526677f3c6686bb615822dcf5efe6bc
kv: make delete range optional on number of keys

Actually, we may only wanna let the objects with real big number of omap to
use delete range. if not, we find too many tombstones will have side-effects
on performance of kv.

refer: https://github.com/facebook/rocksdb/wiki/DeleteRange-Implementation

Signed-off-by: Zengran Zhang <zhangzengran@sangfor.com.cn>
src/common/options.cc
src/kv/RocksDBStore.cc
src/kv/RocksDBStore.h