[
https://issues.apache.org/jira/browse/TS-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922265#comment-13922265
]
Leif Hedstrom commented on TS-2604:
-----------------------------------
Gotcha. So there is a simpler way to deal with this (IMO), which is this:
1. Enable read-while-writer.
2. Make a plugin that watches for requests (cache miss), and decide if it's
likely cacheable or not.
3. If the plugin decides a request (cache miss) is likely cacheable, enable the
following two overridable configurations:
{code}
proxy.config.http.cache.max_open_read_retries
proxy.config.http.cache.open_read_retry_time
{code}
The issue setting those setting always is that for uncacheable content, it'll
impose serious latency. Hence, doing this selectively would achieve connection
collapsing when appropriate, without a lot of additional code.
I haven't looked (much) at your patch, but it feels that you have most of
what's necessary in place. But if so, why not go this route of letting ATS do
the collapsing for you when appropriate ?
> Collapsed connection plugin
> ---------------------------
>
> Key: TS-2604
> URL: https://issues.apache.org/jira/browse/TS-2604
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Ethan Lai
> Assignee: Bryan Call
> Labels: review
> Fix For: 5.0.0
>
>
> This plugin collapses connections with identical CacheUrl/EffectiveUrl.
> Please find more detail from README and state.png (State Diagram)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
