Firstly thanks for advice, we are trying to use parent.config, but we have problems on it.when trafficserver is up, it is direct going to parent origin server, I always see parent hit ats' access log while origin server is up on remap.config our parent.config is dest_ip=10.31.25.5 parent="10.31.25.6:80" parent_is_proxy=false round_robin=true parent_retry=unavailable_server_retry unavailable_server_retry_responses=500,502,503 our remap.config map http://10.31.24.4/ http://10.31.25.5/ On Saturday, December 23, 2017, 7:52:34 PM GMT+3, John Rushford <[email protected]> wrote: We use parent.config to provide redundancy and load balance over origins.See here for info on configuring parent.config. https://docs.trafficserver.apache.org/en/latest/admin-guide/files/parent.config.en.html?highlight=parent%20config#std:configfile-parent.config
On Dec 23, 2017, at 9:28 AM, Miles Libbey <[email protected]> wrote: On Sat, Dec 23, 2017 at 8:16 AM, Alan Carroll <[email protected]> wrote: You can also use DNS round robin along with setting the server retries to a non-zero value. Will that "save" the first request to the dead origin? (or would the error make its way back to the user?) On Sat, Dec 23, 2017 at 10:07 AM, Leif Hedstrom <[email protected]> wrote: Yeh you can do this with parent.config or possibly the escalate plugin. The escalate plugin works on missing objects, not dead servers. For instance, perhaps origin1 periodically gets its data from masterorigin, but, sometimes fails. The escalate plugin would have you go to masterorigin when origin1 said it didn't have the content. I’d favor the former if possible, it has a new feature to go to an alternative parent/origin on specified errors, as well as load balancing etc. — Leif On Dec 23, 2017, at 5:51 AM, Burak Sarp <[email protected]> wrote: Hi all, Is there any way to cover origin server failover cases on ATS ? I mean if origin server is down, ATS will try another origin server.. Thanks, Sarp
