DOCSP-23774 arm64 note (#1557)

jason-price-mongodb · jason-price-mongodb · web-flow · commit a86b903580fa · 2022-08-04T13:53:35.000-07:00
* DOCSP-23774-arm64-note * DOCSP-23774-arm64-note * DOCSP-23774-arm64-note * DOCSP-23774-arm64-note * DOCSP-23774-arm64-note * DOCSP-23774-arm64-note Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com>
diff --git a/source/includes/diagnostic-backtrace-generation.rst b/source/includes/diagnostic-backtrace-generation.rst
@@ -0,0 +1,13 @@
+Starting in MongoDB 4.4 running on Linux:
+
+- When the :binary:`~bin.mongod` and :binary:`~bin.mongos` processes
+  receive a ``SIGUSR2`` signal, backtrace details are added to the logs
+  for each process thread.
+
+- Backtrace details show the function calls for the process, which can
+  be used for diagnostics and provided to MongoDB Support if required.
+
+The backtrace functionality is available for these architectures:
+
+- ``x86_64``
+- ``arm64`` (starting in MongoDB 4.4.15, 5.0.10, and 6.0)
diff --git a/source/release-notes/4.4.txt b/source/release-notes/4.4.txt
@@ -2164,13 +2164,9 @@ Support for ``$natural`` Sort on Views
 Support for Diagnostic Backtrace Generation
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Starting in MongoDB 4.4, :binary:`~bin.mongod` and :binary:`~bin.mongos`
-processes running on Linux will now log a backtrace for each of their
-running threads upon receipt of a ``SIGUSR2`` signal. This backtrace can
-be analyzed for diagnostic information or provided to MongoDB support as
-needed. This functionality is currently available only on the ``x86_64``
-architecture. For more information on using this feature, see
-:ref:`sigusr2-diagnostic-backtrace`.
+.. include:: /includes/diagnostic-backtrace-generation.rst
+
+For more information, see :ref:`sigusr2-diagnostic-backtrace`.
 
 Container-aware FTDC Reporting
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
diff --git a/source/release-notes/6.0.txt b/source/release-notes/6.0.txt
@@ -701,6 +701,12 @@ connection object has the following new methods:
 - :method:`Mongo.getWriteConcern()` returns the :term:`write concern`
 - :method:`Mongo.setWriteConcern()` sets the :term:`write concern`
 
+Support for Diagnostic Backtrace Generation in ``arm64``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Starting in MongoDB 6.0 (and 5.0.10, 4.4.15), :ref:`diagnostic backtrace
+generation <sigusr2-diagnostic-backtrace>` in ``arm64`` is supported.
+
 Changes Affecting Compatibility
 -------------------------------
 
diff --git a/source/tutorial/manage-mongodb-processes.txt b/source/tutorial/manage-mongodb-processes.txt
@@ -206,12 +206,7 @@ Troubleshoot ``mongod`` Processes
 Generate a Backtrace
 ~~~~~~~~~~~~~~~~~~~~
 
-Starting in MongoDB 4.4, :binary:`~bin.mongod` and :binary:`~bin.mongos`
-processes running on Linux will now log a backtrace for each of their
-running threads upon receipt of a ``SIGUSR2`` signal. This backtrace can
-be analyzed for diagnostic information or provided to MongoDB support as
-needed. This functionality is currently available only on the ``x86_64``
-architecture.
+.. include:: /includes/diagnostic-backtrace-generation.rst
 
 To issue a ``SIGUSR2`` signal to a running :binary:`~bin.mongod`
 process, use the following command:
