This mostly is just removing the commands from the man page ceph(1). I
left the legacy section in doc/cephfs/administration.rst as-is.
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
Signed-off-by: Bara Ancincova <bara@redhat.com>
https://bugzilla.redhat.com/show_bug.cgi?id=1368528
From email conversation with Sage and Sam:
I don't think it is used at all, and at a minimum it is
untested and undocumented and the implementation is alomst
certainly incomplete.
I definitely support removing any trace of it from the docs.
sage
Prior to this change, the documention instructed administrators to
delete rulesets and users, but did not go into details regarding how to
do that.
Add example commands that admins may use to search for rulesets and
users that might reference the to-be-deleted pool.
Signed-off-by: Ken Dreyer <kdreyer@redhat.com>
* Some CRUSH_TUNABLES$N references were false.
* The explanations concerning the warning when tunables are
non-optimal were false or confusing.
* Make the definition of the "default" profile clearer.
Signed-off-by: François Lafont <francois.lafont@ac-versailles.fr>
* The flush/evict won't work if target_max_bytes/objects are not configured.
* All client requests will be blocked only when target_max_bytes/objects
are reached. Hitting on cache_target_full_ratio will not block client
requests.
Signed-off-by: Yuan Zhou <yuan.zhou@intel.com>
There is a typo in document "Monitoring OSDs and PGs" as below
An OSD was ``down``, was restared, and is now ``recovering``.
This patch corrects 'restared' to 'restarted'. The whole code base
is also searched to ensure there is no more 'restared'.
Signed-off-by: Yilong Zhao <accelazh@gmail.com>
ceph osd pool set $POOL scrub_min_interval N
ceph osd pool set $POOL scrub_max_interval N
ceph osd pool set $POOL deep_scrub_interval N
If N > 0, this value is used for the pool instead of
the corresponding global parameter from the config
(osd_scrub_min_interval, osd_scrub_max_interval or
osd_deep_scrub_interval).
Fixes: #13077
Signed-off-by: Mykola Golub <mgolub@mirantis.com>
This reverts commit 30810da4b5.
After some discussion we have decided it is better to build a generic
dictionary in pg_pool_t to store infrequently used per-pool properties.
Signed-off-by: Sage Weil <sage@redhat.com>
ceph osd pool set $POOL scrub_min_interval N
ceph osd pool set $POOL scrub_max_interval N
ceph osd pool set $POOL deep_scrub_interval N
If N > 0, this value is used for the pool instead of
the corresponding global parameter from the config
(osd_scrub_min_interval, osd_scrub_max_interval or
osd_deep_scrub_interval).
Fixes: #13077
Signed-off-by: Mykola Golub <mgolub@mirantis.com>
These haven't existed since 0.84 -- the cephfs documentation
was updated at the time, but there were also references in the
rados documentation.
Signed-off-by: John Spray <john.spray@redhat.com>
always indent using tab, the rendered html looks good, but it helps with
editor to highlight the codeblock properly.
Signed-off-by: Kefu Chai <kchai@redhat.com>
doc/rados/operations/add-or-rm-mons: simplify the steps to add a mon
Reviewed-by: Joao Eduardo Luis <joao@suse.de>
Reviewed-by: Sage Weil <sage@redhat.com>
Reviewed-by: Loic Dachary <ldachary@redhat.com>
this change removes the step to "ceph mon add" before starting a new
monitor. because the existing leader will start an election at seeing
the MMonJoin message sent by the new joiner, after the quorum is
archieved, the monmap will be updated with the new monitor.
so, "ceph mon add" is not necessary to add a new monitor.
moreover, this command will be blocked until a new quorum is formed,
and the proposed monmap is accepted. but in case of adding a monitor
to a single monitor cluster, the leader will wait until at least two
of the monitors reply to it. apparently, this does not happen unless
the new monitor starts. so from the user's point of view, this
command hangs until timesout, if he/she does not start the mon.b
beforehand. but this is an expected behaviour.
so, to avoid this confusion and simplify the steps to add a new
monitor. we'd better simply remove this "ceph mon add" step.
Fixes: #12620
Signed-off-by: Kefu Chai <kchai@redhat.com>
Wip writeback throttling for cache tiering
This patch is to do write back throttling for cache tiering, which is similar to what the Linux kernel does for page cache write back. A paramter 'cache_target_dirty_high_ratio' (default 0.6) is introduced as the high speed flushing threshold, while leave the 'cache_target_dirty_ratio' (default 0.4) to represent the low speed threshold. The flush speed is controlled by limiting the parallelism of flushing. The maximum parallelism under low speed is half of the parallelism under high speed. If there is at least one PG such that the dirty ratio beyond the high threshold, full speed mode is entered; If there is no PG such that dirty ratio beyond the low threshold, idle mode is entered; In other cases, slow speed mode is entered.
Signed-off-by: Mingxin Liu <mingxinliu@ubuntukylin.com>
Reviewed-by: Li Wang <liwang@ubuntukylin.com>
Suggested-by: Nick Fisk <nick@fisk.me.uk>
Tested-by: Kefu Chai <kchai@redhat.com>
Explain the significance of pgp num & how it differs from pg num.
Fixes: #10035
Reported-by: Loic Dachary <loic@dachary.org>
Signed-off-by: Abhishek Lekshmanan <abhishek.lekshmanan@ril.com>
Specified crush-ruleset-name is required to exist, implicit creation is
going to happen only if crush-ruleset-name wasn't specified on the
command line. While at it, pool-name is very much a required param.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
ceph osd setmap command was disabled and subsequently removed 5 years
ago. See 9aadd41b2095 ("mon: disable 'osd setmap'") and 6d292397aa26
("mon: remove dead 'setmap' code").
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Mention that "ceph tell osd.N bench" will not overwrite data in a live
OSD, but might temporarily affect OSD performance.
Signed-off-by: Florian Haas <florian@hastexo.com>
* nodelete - pool can't be deleted
* nopgchange - pool's pg and pgp num can't be changed
* nosizechange - pool's size and min size can't be changed
This is intended to help some poor admin to avoid a very bad day.
Fixes: #9792 (but in a different way than it was proposed there)
Signed-off-by: Mykola Golub <mgolub@mirantis.com>
undersized not valid: undersized not in inactive|unclean|stale
undersized not valid: undersized doesn't represent an int
Invalid command: unused arguments: ['undersized']
pg dump_stuck {inactive|unclean|stale [inactive|unclean|stale...]} {<int>} : show information about stuck pgs
Signed-off-by: xinxin shu <xinxin.shu@intel.com>
A short introduction to the first time user of an erasure coded pool.
It includes a reminder of how it relates to cache tiering and links to
define new profiles with an example.
There was examples in the developer documentation but the operator
expects to find such a guide in the rados operations chapter.
http://tracker.ceph.com/issues/9970Fixes: #9970
Signed-off-by: Loic Dachary <ldachary@redhat.com>
LRC now uses Jerasure as the default EC backend. But it is actually
possible to switch to other backend like Isa using the low level
configuration. This commits Adds documents on how to specify the EC
backend in each LRC layer:
Signed-off-by: Yuan Zhou <yuan.zhou@intel.com>
