Hi, We’ve been using the Thundering Herd protection provided by Read While Writer, Open Read Retry Timeout and Open Write Fail Action and have been getting some great results. However the behavior seems to change when we start using parent.config in order to provide some simple origin failover (I.e simple Primary/Secondary Origin kind of thing). My initial tests are showing multiple access failures and not very much in the way of request coalescing.
I don’t all have the details with me now, but at a high level, should we expect Read While Writer, Open Read Retry Timeout and Open Write Fail Action to all work in the same way when proxy.config.http.parent_proxy_routing_enable is enabled and we have a simple Primary/Secondary Origin configured with "parent_is_proxy=false”? Especially when most of the time the Primary Origin will be up and available. Are there any gotchas we should be aware of? All this testing is with ATS 7.0 currently. Thanks for your insight. Nick Nick Dunkin Principal Engineer o: 678.258.4071 e: [email protected]<mailto:[email protected]> 4375 River Green Pkwy # 100, Duluth, GA 30096, USA [cid:902550A1-F59F-4EDA-B98A-FF0B12771D75]
