ocket8888 opened a new issue #3537: Duplicate Origin Problem URL: https://github.com/apache/trafficcontrol/issues/3537 When two or more Delivery Services share one or more origins, the output of a `parent.config` for any given Cache Server is indeterminate. This has been discussed [on the dev mailing list](https://mail-archives.apache.org/mod_mbox/trafficcontrol-dev/201902.mbox/%3C413C9A64-ADA3-4A42-AE5D-613E086C5997%40gmail.com%3E) but thus far no strategy to deal with it has been agreed upon. Specifically, the problem occurs whenever the origins have the same FQDN but some other part of the generated `remap.config` line would be different. This can (and will) happen in the following scenarios: - When one DS has Query String Handling configured to 0 or 1 and the other has it configured to 2 - When one DS is of type HTTP_LIVE, HTTP_NO_CACHE, or DNS_LIVE and the other is none of those - Whenever the two DSes have differing "Raw Remap Text" fields (unless exactly one of them is of the ANY_MAP type and happens to have a "Raw Remap Text" field that exactly matches the line generated by Traffic Ops for the other DS) - One Delivery Service has a Profile and that profile has an `algorithm` parameter for the `parent.config` file with a value other than `round_robin` - Both Delivery Services have Profiles, and they have different values for the `algorithm` parameter for the `parent.config` file. That list isn't exhaustive, just what I've come up with so far.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
