Hi, I have a parent.config rule that uses a primary and secondary set of parents.
Assuming a 404 from a parent in the primary list I would like to immediately try a parent in the secondary parent list, but for a 5xx, or connection error, I would like to first exhaust the primary list first, before then trying the secondary. I would imagine this is a fairly common use case for cluster failover behavior. i.e. “Content is HTTP 404 form cluster A, so go to cluster B” I am not able to get this use case working with the various options for secondary_mode in parent.config (ATS ver 9.1.3). Please can anyone provide assistance? Maybe this use case is supported with strategies.yaml? Thanks Nick Nick Dunkin Director, Software Architecture Manager – Architecture and New Product Introduction o: +1 678.258.4071 e: nick.dun...@vecima.com<mailto:nick.dun...@vecima.com> [cidimage001.png@01D6CC8C.6FC5A580]
