From 0ad9f89d53c2f21cf3575e948b4533f793cd1b26 Mon Sep 17 00:00:00 2001 From: Stellios Williams Date: Mon, 23 Jun 2025 20:54:31 +1000 Subject: [PATCH] doc: Fixed a spelling error. Corrected communicte to communicate Signed-off-by: Instelligence.io (cherry picked from commit c328902e3929d9841f952948b0336ec5b20d36fa) --- doc/rados/operations/stretch-mode.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/rados/operations/stretch-mode.rst b/doc/rados/operations/stretch-mode.rst index ed9c72b0dc827..d79322ae6ff18 100644 --- a/doc/rados/operations/stretch-mode.rst +++ b/doc/rados/operations/stretch-mode.rst @@ -64,7 +64,7 @@ you might discover that your cluster does not satisfy those constraints. The first category of these failures that we will discuss involves inconsistent networks. If there is a netsplit (a failure that -splits the network into two conceptual islands that cannot communicte with +splits the network into two conceptual islands that cannot communicate with each other), Ceph might be unable to mark OSDs ``down`` and remove them from Placement Group (PG) acting sets. This failure to mark ODSs ``down`` will occur despite the fact that the primary PG is unable to replicate data (a -- 2.39.5