rawlinp commented on issue #1908: Changes for Backup Edge Cache Group URL: https://github.com/apache/incubator-trafficcontrol/pull/1908#issuecomment-368973959 I think we want to allow the `backupList` to be used for compartmentalizing traffic but also provide a configurable option to fallback to the default behavior of finding the next closest cachegroup once all `backupList` cachegroups have been exhausted. Perhaps by default we will fall back to finding the next closest cachegroup if all backup cachegroups have been exhausted, but if the coverageZone has a field `"fallbackToNextClosest": false` the request will be dropped if the `backupList` has been exhausted? Maybe the format changes to: ``` "GROUP2": { "backupZones": { "list": ["GROUP1"], "fallbackToNextClosest": false <-----default: true or false? }, "network6": [ "1234:567a::/64", "1234:567b::/64" ], "network": [ "10.197.69.0/24" ] } ``` I'm not sure it matters whether the default is true or false as long as it's documented. What do you guys think?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
