Skip to content

Commit

Permalink
doc: deprecate the cache tiering
Browse files Browse the repository at this point in the history
This topic has been discussed many times; recently at the Dev
Summit of Cephalocon 2023.

This commit is the minial version of the work, contained entirely
within the `doc`. However, likely it will be expanded as there
were ideas like e.g. adding cache tiering back experimental feature
list (Sam) to warn users when deploying a new cluster.

Signed-off-by: Radosław Zarzyński <[email protected]>
  • Loading branch information
rzarzynski committed May 17, 2023
1 parent cd5bf7d commit 535b8db
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 0 deletions.
1 change: 1 addition & 0 deletions PendingReleaseNotes
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,7 @@
`ceph config set mgr mgr/telemetry/leaderboard_description ‘Cluster description’`.
* CEPHFS: After recovering a Ceph File System post following the disaster recovery
procedure, the recovered files under `lost+found` directory can now be deleted.
* core: cache-tiering is now deprecated.

>=17.2.1

Expand Down
4 changes: 4 additions & 0 deletions doc/rados/operations/cache-tiering.rst
Original file line number Diff line number Diff line change
@@ -1,6 +1,10 @@
===============
Cache Tiering
===============
.. warning:: Cache tiering has been deprecated in the Reef release as it
has lacked a maintainer for a very long time. This does not mean
it will be certainly removed, but we may choose to remove it
without much further notice.

A cache tier provides Ceph Clients with better I/O performance for a subset of
the data stored in a backing storage tier. Cache tiering involves creating a
Expand Down

0 comments on commit 535b8db

Please sign in to comment.