From: Zengran Zhang Date: Tue, 2 Apr 2019 14:03:45 +0000 (+0800) Subject: kv: make delete range optional on number of keys X-Git-Tag: v14.2.3~54^2~1 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=cc3e208cad4474ff45e11f9da4d07489b47804d4;p=ceph.git 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 (cherry picked from commit b039e63c6816ed371c6db975b4cbc7a3d170bb1f) --- diff --git a/src/common/options.cc b/src/common/options.cc index 0d0cbe5fe2ee..f5ca18a17149 100644 --- a/src/common/options.cc +++ b/src/common/options.cc @@ -3935,7 +3935,12 @@ std::vector