[
https://issues.apache.org/jira/browse/TS-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-375.
------------------------------
Resolution: Fixed
This is already fixed, see
proxy.config.cache.mutex_retry_delay
> Expose MUTEX_RETRY_DELAY HRTIME_MSECONDS as a configurable option?
> ------------------------------------------------------------------
>
> Key: TS-375
> URL: https://issues.apache.org/jira/browse/TS-375
> Project: Traffic Server
> Issue Type: New Feature
> Components: TS API
> Reporter: Leif Hedstrom
> Priority: Minor
> Fix For: 3.1
>
>
> Would it make sense to expose MUTEX_RETRY_DELAY HRTIME_MSECONDS as a
> configurable option? It would allow a very skilled user to tweak the lock
> rescheduling to fit her application, HW and load patterns "optimally". This
> would be a "stop-gap" solution for some situations, until we can reduce /
> eliminate some of the rescheduling that happens (and it would be very
> "application" specific).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
