From 07f60d4505d1ea235e49c19fe34a8a82b2390116 Mon Sep 17 00:00:00 2001 From: John Wilkins Date: Wed, 7 Nov 2012 14:05:15 -0800 Subject: [PATCH] doc: Added topic for adding OSDs and adjusting CRUSH weights. Signed-off-by: John Wilkins --- doc/cluster-ops/add-or-rm-osds.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/cluster-ops/add-or-rm-osds.rst b/doc/cluster-ops/add-or-rm-osds.rst index 170347991651..ec24315ea54c 100644 --- a/doc/cluster-ops/add-or-rm-osds.rst +++ b/doc/cluster-ops/add-or-rm-osds.rst @@ -134,6 +134,15 @@ hard disks than older hosts in the cluster (i.e., they may have greater weight). ceph osd crush set {id} {name} {weight} [{bucket-type}={bucket-name}, ...] +.. topic:: Argonaut (v0.48) Best Practices + + To limit impact on user I/O, add an OSD to the CRUSH map with an initial + weight of ``0``. Then, ramp up the CRUSH weight a little bit at a time + (e.g., ``0.2``) and allow migration to complete. Continue to increment + the CRUSH weight until you reach your desired CRUSH weight. This practice + will no longer be necessary in Bobtail and subsequent releases. + + Adding an OSD (Chef) -------------------- -- 2.47.3