[GitHub] [trafficserver] ezelkow1 edited a comment on issue #8555: Stop write_fail actions from going to origin if parentage with go_direct=false

[GitBox <gi...@apache.org>]

ezelkow1 edited a comment on issue #8555:
URL: https://github.com/apache/trafficserver/issues/8555#issuecomment-995049702


   @traeak may have some logs, later, since he can reproduce this in a lab. I believe it comes down to this section, 
   https://github.com/apache/trafficserver/blob/master/proxy/http/HttpTransact.cc#L3269
   
   In the else case there we have exhausted all write lock attempts at which point I believe that how_to_open_connection will just send the sm direct to the origin, bypassing parents. Its just an educated guess at this point though
   
   This is with proxy.config.http.cache.open_write_fail_action INT 0, you need to generate contention on the write lock that will fail by having an origin stall upstream of a parent, but still accept connections so that parentage will not mark down the origin. It basically creates a scenario where parents cannot mark down, even though no data is received, requests stack up and run through read_retries, then write_retries and eventually go to the origin


-- 
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: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org