[
https://issues.apache.org/jira/browse/TS-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035005#comment-13035005
]
Leif Hedstrom commented on TS-621:
----------------------------------
I think I've found a problem on clustering here. I'm fetching e.g.
curl -D - -o /dev/null -s -x cluster1.ogre.com:8080
http://www.howstuffworks.com/bearing/
So, this 301 gets cached on cluster1, I'm assuming the hashing on the URL does
that. But if I fetch the same object from cluster2.ogre.com:8080, it's always a
cache miss. And to make things worse, it actually forces cache1 to refresh the
object as well (so it gets refetched, and updated in cache).
Also, it seems that 40x's are always cached in cluster mode now, even with the
proxy.config.http.negative_caching_enabled setting disabled.
Neither of these problems seems to occur in the standalone cache scenario. I'll
try to do some more debugging on this as well, and yes, I know we already
suspect issues with clustering. John, you have any immediate ideas we should
look into? :)
> writing 0 bytes to the HTTP cache means only update the header... need a new
> API: update_header_only() to allow 0 byte files to be cached
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TS-621
> URL: https://issues.apache.org/jira/browse/TS-621
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 2.1.5
> Reporter: John Plevyak
> Assignee: John Plevyak
> Fix For: 2.1.9
>
> Attachments: ts-621-jp-1.patch, ts-621-jp-2.patch, ts-621-jp-3.patch
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
