From bb83122d18d64366199b3b1b44ecb4ff50c493fe Mon Sep 17 00:00:00 2001 From: Satoru Takeuchi Date: Wed, 25 Mar 2020 10:37:05 +0000 Subject: [PATCH] ceph: fix a wrong comment "comment" here should mean the comments of `pg_autoscaler` in cluster/examples/kubernetes/ceph/cluster.yaml. However, it's ambiguous. It's straightforward to use "add". Signed-off-by: Satoru Takeuchi --- Documentation/ceph-advanced-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ceph-advanced-configuration.md b/Documentation/ceph-advanced-configuration.md index dd80a1490..6c08500a0 100644 --- a/Documentation/ceph-advanced-configuration.md +++ b/Documentation/ceph-advanced-configuration.md @@ -243,7 +243,7 @@ a common practice for those looking to target certain workloads onto faster > checkout [Ceph New in Nautilus: PG merging and autotuning](https://ceph.io/rados/new-in-nautilus-pg-merging-and-autotuning/) article. > > To enable the `pg_autoscaler` module automatically in a Rook Ceph cluster, -> you can comment in the `pg_autoscaler` entry in the `spec.mgr.modules` +> you can add the `pg_autoscaler` entry in the `spec.mgr.modules` > struct of CephCluster CRD. The general rules for deciding how many PGs your pool(s) should contain is: