From 524db4609f5f0b4639828b327cfc972243e08ce7 Mon Sep 17 00:00:00 2001 From: Anthony D'Atri Date: Fri, 11 Apr 2025 10:29:52 -0400 Subject: [PATCH] doc/cephadm: Add admonition re restarting an OSD service Signed-off-by: Anthony D'Atri --- doc/cephadm/operations.rst | 18 ++++++++++++------ doc/cephadm/services/osd.rst | 7 +++++++ 2 files changed, 19 insertions(+), 6 deletions(-) diff --git a/doc/cephadm/operations.rst b/doc/cephadm/operations.rst index 22d91c39b0622..c6aeedd9d01a2 100644 --- a/doc/cephadm/operations.rst +++ b/doc/cephadm/operations.rst @@ -51,17 +51,23 @@ You can stop, start, or restart a daemon with: .. prompt:: bash # - ceph orch daemon stop - ceph orch daemon start - ceph orch daemon restart + ceph orch daemon stop + ceph orch daemon start + ceph orch daemon restart You can also do the same for all daemons for a service with: .. prompt:: bash # - ceph orch stop - ceph orch start - ceph orch restart + ceph orch stop + ceph orch start + ceph orch restart + +.. note:: + It is usually not safe to run ``ceph orch restart osd.myosdservice`` on a + running cluster, as attention is not paid to CRUSH failure domains, and + parallel OSD restarts may lead to temporary data unavailability or in rare + cases even data loss. Redeploying or reconfiguring a daemon diff --git a/doc/cephadm/services/osd.rst b/doc/cephadm/services/osd.rst index ed9b846052a1e..2dce4a99889a2 100644 --- a/doc/cephadm/services/osd.rst +++ b/doc/cephadm/services/osd.rst @@ -1215,6 +1215,13 @@ This example applies to two hosts: ``ceph01`` and ``ceph04``. post pertinent to its development can be seen here:* `Eugen Block's "Cephadm: Activate existing OSDs" blog post `_. +.. note:: + It is usually not safe to run ``ceph orch restart osd.myosdservice`` on a + running cluster, as attention is not paid to CRUSH failure domains, and + parallel OSD restarts may lead to temporary data unavailability or in rare + cases even data loss. + + Further Reading =============== -- 2.39.5