[trafficserver] branch 9.2.x updated: Doc: Add proxy.config.cacvhe.mutex_retry_delay (#8376)

[zw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 9.2.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/9.2.x by this push:
     new 05df9d43b Doc: Add proxy.config.cacvhe.mutex_retry_delay (#8376)
05df9d43b is described below

commit 05df9d43b4110bf574d2140a2233104c7678cdd4
Author: Alan M. Carroll <am...@apache.org>
AuthorDate: Tue Oct 5 14:12:37 2021 -0500

    Doc: Add proxy.config.cacvhe.mutex_retry_delay (#8376)
    
    (cherry picked from commit 3ad1587676ef82615c7ab0b2ef8e935cc2fb7356)
---
 doc/admin-guide/files/records.config.en.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/doc/admin-guide/files/records.config.en.rst b/doc/admin-guide/files/records.config.en.rst
index 80e8b3037..fe9925dae 100644
--- a/doc/admin-guide/files/records.config.en.rst
+++ b/doc/admin-guide/files/records.config.en.rst
@@ -2428,6 +2428,17 @@ Cache Control
    write vector. For further details on cache write vectors, refer to the
    developer documentation for :cpp:class:`CacheVC`.
 
+.. ts::cv:: CONFIG proxy.config.cache.mutex_retry_delay INT 2
+   :reloadable:
+   :units: milliseconds
+
+   The retry delay for missing a lock on a mutex in the cache component. This is used generically
+   for most locks, except those that have an explicit configuration for the retry delay. For
+   instance, if the cache component is notifying another continuation of a cache event and fails to
+   get the lock for that continuation, it will use this as the delay for the retry. This is also
+   used from the asynchronous IO threads when IO finishes and the ``CacheVC`` lock or stripe lock is
+   required.
+
 RAM Cache
 =========