From eae07da6252ce59197a376ef9bec72cadecd8e0b Mon Sep 17 00:00:00 2001 From: "Alan M. Carroll" Date: Tue, 5 Oct 2021 10:56:34 -0500 Subject: [PATCH] Doc: Add proxy.config.cacvhe.mutex_retry_delay --- 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 7a226a5585f..2172d43789b 100644 --- a/doc/admin-guide/files/records.config.en.rst +++ b/doc/admin-guide/files/records.config.en.rst @@ -2395,6 +2395,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 =========