From 1becb47b4d9414b3aefe6bb38398bc03de5e2c39 Mon Sep 17 00:00:00 2001 From: Paul Emmerich Date: Fri, 5 Jun 2020 13:54:15 +0200 Subject: [PATCH] mds: make threshold for MDS_TRIM configurable Fixes: https://tracker.ceph.com/issues/45906 Signed-off-by: Paul Emmerich (cherry picked from commit d905678a87326195c71ce6da16933e671b0d90eb) --- doc/cephfs/health-messages.rst | 4 ++-- src/common/options.cc | 6 ++++++ src/mds/Beacon.cc | 4 ++-- 3 files changed, 10 insertions(+), 4 deletions(-) diff --git a/doc/cephfs/health-messages.rst b/doc/cephfs/health-messages.rst index aa93a9d7142..b096e124c97 100644 --- a/doc/cephfs/health-messages.rst +++ b/doc/cephfs/health-messages.rst @@ -59,8 +59,8 @@ by the setting ``mds_log_max_segments``, and when the number of segments exceeds that setting the MDS starts writing back metadata so that it can remove (trim) the oldest segments. If this writeback is happening too slowly, or a software bug is preventing trimming, then this health -message may appear. The threshold for this message to appear is for the -number of segments to be double ``mds_log_max_segments``. +message may appear. The threshold for this message to appear is controlled by +the config option ``mds_log_warn_factor``, the default is 2.0. Message: "Client *name* failing to respond to capability release" Code: MDS_HEALTH_CLIENT_LATE_RELEASE, MDS_HEALTH_CLIENT_LATE_RELEASE_MANY diff --git a/src/common/options.cc b/src/common/options.cc index 149d14db7c8..bef638278fe 100644 --- a/src/common/options.cc +++ b/src/common/options.cc @@ -7848,6 +7848,12 @@ std::vector