[
https://issues.apache.org/jira/browse/TS-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933810#action_12933810
]
Zhao Yongming commented on TS-532:
----------------------------------
I have finally get the root cause:
my OS is 2 squid cluster, while one of the cluster have no dedicate hosts file,
then fall back to DNS to lookup the backend, then loop back to my TS.
this will just happens when both TS and Squid have no such content in the
cache, and you have send a HEAD request.
the question:
the loop detect in Squid and TS seems all fail for me. why?
> possible misbehavior with HEAD request before GET
> -------------------------------------------------
>
> Key: TS-532
> URL: https://issues.apache.org/jira/browse/TS-532
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Environment: we have many haproxy before the TS server, do L7 hashing
> for all request
> Reporter: Zhao Yongming
> Priority: Trivial
> Attachments: 35425.cap, 434.cap, 8092.cap
>
>
> sometimes there is many HEAD request flood in, looks like cache in loop, but
> TS does not identify it as a loop.
> as the HEAD request will all pass to OS, that will make OS unable to response
> for sometime? get 1-5k connections, make TS get throttling.
> here is some tcpdum cap file
> why I suspect HEAD request, is when I ban all HEAD request use quick filter
> mask, the connection rush is gone.
> but this could be other problem indeed. just open this bug for logging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
