From 8e81b0d7e1bc9bf776549687a8e07374dcbde5e2 Mon Sep 17 00:00:00 2001 From: Loic Dachary Date: Wed, 8 Apr 2015 19:33:05 +0200 Subject: [PATCH] doc: an erasure code crush ruleset can be dynamically modified Signed-off-by: Loic Dachary --- doc/rados/troubleshooting/troubleshooting-pg.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/rados/troubleshooting/troubleshooting-pg.rst b/doc/rados/troubleshooting/troubleshooting-pg.rst index e7af5a54b6d8..b761cce5f175 100644 --- a/doc/rados/troubleshooting/troubleshooting-pg.rst +++ b/doc/rados/troubleshooting/troubleshooting-pg.rst @@ -432,9 +432,8 @@ mapping. It can be resolved by: coded pool to be modified, it will become clean automatically) * use a hand made CRUSH ruleset that tries more times to find a good - mapping. (that requires the creation of another pool as erasure - code profiles cannot be dynamically modified). It can be done by - setting ``set_choose_tries`` to a value greater than the default. + mapping. It can be done by setting ``set_choose_tries`` to a value + greater than the default. You should first verify the problem with ``crushtool`` after extracting the crushmap from the cluster so your experiments do not -- 2.47.3