[
https://issues.apache.org/jira/browse/TS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-658:
------------------------------
Fix Version/s: (was: 5.2.0)
sometime
> HTTP SM holds the cache write lock for too long
> -----------------------------------------------
>
> Key: TS-658
> URL: https://issues.apache.org/jira/browse/TS-658
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Assignee: Alan M. Carroll
> Labels: A
> Fix For: sometime
>
>
> It seems we open the cache for write very early on in the HTTP SM, which can
> have very bad effect on performance if the object is not cacheable. It's not
> totally clear as to why this is done this way, but we should examine this for
> v3.1, and try to minimize how long we hold the lock. It's possible this is
> related to read_while_writer, but then it should be modified IMO.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
