mirror of
https://github.com/ceph/ceph
synced 2024-12-28 14:34:13 +00:00
dd81858ca6
--osd-pool-default-crush-replicated-ruleset replaces --osd-pool-default-crush-rule If --osd-pool-default-crush-rule is set it takes precedence over --osd-pool-default-crush-replicated-ruleset and a deprecation warning is displayed. The CrushWrapper::get_osd_pool_default_crush_replicated_ruleset helper is used to implement this behaviour. Signed-off-by: Loic Dachary <loic@dachary.org>
34 lines
1.6 KiB
Plaintext
34 lines
1.6 KiB
Plaintext
v0.74
|
|
~~~~~
|
|
|
|
- We now default to the 'bobtail' CRUSH tunable values that are first supported
|
|
by Ceph clients in bobtail (v0.48) and Linux kernel version v3.9. If you
|
|
plan to access a newly created Ceph cluster with an older kernel client, you
|
|
should use 'ceph osd crush tunables legacy' to switch back to the legacy
|
|
behavior. Note that making that change will likely result in some data
|
|
movement in the system, so adjust the setting before populating the new
|
|
cluster with data.
|
|
|
|
- We now set the HASHPSPOOL flag on newly created pools (and new
|
|
clusters) by default. Support for this flag first appeared in
|
|
v0.64; v0.67 Dumpling is the first major release that supports it.
|
|
It is first supported by the Linux kernel version v3.9. If you plan
|
|
to access a newly created Ceph cluster with an older kernel or
|
|
clients (e.g, librados, librbd) from a pre-dumpling Ceph release,
|
|
you should add 'osd pool default flag hashpspool = false' to the
|
|
'[global]' section of your 'ceph.conf' prior to creating your
|
|
monitors (e.g., after 'ceph-deploy new' but before 'ceph-deploy mon
|
|
create ...').
|
|
|
|
- The configuration option 'osd pool default crush rule' is deprecated
|
|
and replaced with 'osd pool default crush replicated ruleset'. 'osd
|
|
pool default crush rule' takes precedence for backward compatibility
|
|
and a deprecation warning is displayed when it is used.
|
|
|
|
v0.72.2
|
|
~~~~~~~
|
|
- As part of fix for #6796, 'ceph osd pool set <pool> <var> <arg>' now
|
|
receives <arg> as an integer instead of a string. This affects how
|
|
'hashpspool' flag is set/unset: instead of 'true' or 'false', it now
|
|
must be '0' or '1'.
|