From: Anthony D'Atri Date: Fri, 11 Apr 2025 14:29:52 +0000 (-0400) Subject: doc/cephadm: Add admonition re restarting an OSD service X-Git-Tag: testing/wip-khiremat-testing-20250424.121018-squid-debug~24^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=91c97628a51ed2132111f763ffad7cc67af07c37;p=ceph-ci.git doc/cephadm: Add admonition re restarting an OSD service Signed-off-by: Anthony D'Atri (cherry picked from commit 524db4609f5f0b4639828b327cfc972243e08ce7) --- diff --git a/doc/cephadm/operations.rst b/doc/cephadm/operations.rst index 22d91c39b06..c6aeedd9d01 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 e5c2541c4ec..fa83c37a435 100644 --- a/doc/cephadm/services/osd.rst +++ b/doc/cephadm/services/osd.rst @@ -1161,6 +1161,13 @@ This procedure assumes the existence of 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 ===============