crimson/os/seastore/segment_cleaner: increase avaliable ratio limit

Journal trimming may consume unexpected number of segments when the
available ratio limit is reached with user transactions blocked, causing
ceph_abort(). So increase the limit as a simple workaround.

Signed-off-by: Yingxin Cheng <yingxin.cheng@intel.com>

diff --git a/src/crimson/os/seastore/async_cleaner.h b/src/crimson/os/seastore/async_cleaner.h
index c75ee6a23510dc8b7f00e387cee788e8e0679135..2d7a73890cb55ce0539310ffee1e5e9b8432b970 100644 (file)
--- a/src/crimson/os/seastore/async_cleaner.h
+++ b/src/crimson/os/seastore/async_cleaner.h
@@ -546,8 +546,8 @@ public:
          12,   // target_journal_segments
          16,   // max_journal_segments
          2,    // target_backref_inflight_segments
-         .1,   // available_ratio_gc_max
-         .05,  // available_ratio_hard_limit
+         .15,  // available_ratio_gc_max
+         .1,   // available_ratio_hard_limit
          .1,   // reclaim_ratio_gc_threshold
          1<<20,// reclaim_bytes_per_cycle
          1<<17,// rewrite_dirty_bytes_per_cycle