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 <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 >> >>
