From: Zac Dover Date: Mon, 24 Jun 2024 10:32:30 +0000 (+1000) Subject: doc/rados: edit troubleshooting-osd.rst X-Git-Tag: v18.2.5~576^2 X-Git-Url: http://git.apps.os.sepia.ceph.com/?a=commitdiff_plain;h=05231a878007662135c7b47ca9fd6f85131d041f;p=ceph.git doc/rados: edit troubleshooting-osd.rst Make minor changes to the "Debugging Slow Requests" section of doc/rados/troubleshooting/troubleshooting-osd.rst in preparation for an expansion of this section in response to a reqeust from Joel Davidow. Signed-off-by: Zac Dover (cherry picked from commit 8b211b9c7f9b173bb12028eb7108d13867883d6e) --- diff --git a/doc/rados/troubleshooting/troubleshooting-osd.rst b/doc/rados/troubleshooting/troubleshooting-osd.rst index 035947d7ec94b..3150e8382ad9d 100644 --- a/doc/rados/troubleshooting/troubleshooting-osd.rst +++ b/doc/rados/troubleshooting/troubleshooting-osd.rst @@ -655,7 +655,7 @@ Events from the OSD as it processes ops: is now being performed. - ``waiting for subops from``: The op has been sent to replica OSDs. -Events from ```Filestore```: +Events from ``Filestore``: - ``commit_queued_for_journal_write``: The op has been given to the FileStore. - ``write_thread_in_journal_buffer``: The op is in the journal's buffer and is waiting @@ -667,7 +667,7 @@ Events from the OSD after data has been given to underlying storage: - ``op_commit``: The op has been committed (that is, written to journal) by the primary OSD. -- ``op_applied``: The op has been `write()'en +- ``op_applied``: The op has been `written with write() `_ to the backing FS (that is, applied in memory but not flushed out to disk) on the primary. - ``sub_op_applied``: ``op_applied``, but for a replica's "subop". @@ -676,8 +676,9 @@ Events from the OSD after data has been given to underlying storage: hears about the above, but for a particular replica (i.e. ````). - ``commit_sent``: We sent a reply back to the client (or primary OSD, for sub ops). -Some of these events may appear redundant, but they cross important boundaries -in the internal code (such as passing data across locks into new threads). +Although some of these events may appear redundant, they cross important +boundaries in the internal code (such as passing data across locks into new +threads). Flapping OSDs