jrushford commented on issue #8789: URL: https://github.com/apache/trafficserver/issues/8789#issuecomment-1098105303
@amoghyermalkar123 You're using the consistent_hash algorithm. So, a hash is created from the request url path. That hash is used to select a parent from a map. The client session is not tied to one specific parent for all requests that it makes. One request may go to parent1 and the next request may go to parent2, etc... the parent chosen is determined by the request URL path. So, a request for a specific object will always go to the same parent when there is a cache miss. It will only use another parent if the one originally chosen is unreachable or if the request response from that parent times out. In your debug, I'm not seeing any of the request URL's, do they vary, are your parallel requests all using just one request? Once the response has been obtained, it should be cached on your child cache. Once cached there will be no further requests to parents for the same object until it expires from the cache. As for the connect error to parent 1, I cannot say from lookin g at your logs. At that time, a connection failure occurred and Parent selection chose another parent to try. A connection error is caused when TCP is unable to establish the connection or the error could have been from a timeout on receiving the response. I've never seen the issue that you've described but will try to duplicate. There are some parent proxy timeout settings in records.config that we should take a look at. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
