From d7a9ff09e6bb8796a1aed64b6d300b7cd6e9da24 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Thu, 5 Jun 2025 13:28:13 +1000 Subject: [PATCH] doc/rados/ops: edit cache-tiering.rst Remove part of a sentence that might have led readers to think that it is a good idea to deploy cache tiering on releases prior to Reef. This incorporates Anthony D'Atri's suggestion from here: https://github.com/ceph/ceph/pull/63614#discussion_r2116020937 Signed-off-by: Zac Dover (cherry picked from commit 3618b1bbbb0096a8a08f59aeb6b7436ef9d0c12e) --- doc/rados/operations/cache-tiering.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/rados/operations/cache-tiering.rst b/doc/rados/operations/cache-tiering.rst index 667d34be6f832..762ec6454b24c 100644 --- a/doc/rados/operations/cache-tiering.rst +++ b/doc/rados/operations/cache-tiering.rst @@ -8,7 +8,7 @@ notice. The upstream Ceph community strongly advises against deploying new cache - tiers to releases after the Reef release. + tiers. 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 -- 2.39.5