-
Notifications
You must be signed in to change notification settings - Fork 81
TO: Should enumerate all origins separately in parent.config #825
Comments
Do you have an example of what that should look like? Comma separated? And where does that list come from that gets assigned? A dropdown of Edges and Mids? |
@mtorluemke Are you sure about this? I'm seeing events here that my Mids reaches the threshold, but they go down only for the specific origin (which is caught by the "."). Other DS are fine. The line in diags.log is deceiving. |
@smalenfant only as sure as I've been convinced -- I don't think we have a lot of empirical data. Anything further you can share? |
@dewrich all of the origins that have special requirements get enumerated already -- code to do that is 1025-1034 of lib/UI/ConfigFiles.pm in master. This change would be to expand that, and replace (remove?) lines 1049-1055 in the same file. Also, today all mids in the cache group serve traffic for all delivery services, unlike at edge tier where you can assign specific edges to a given delivery service. |
@mtorluemke I'm not against this change at all (even would like it if that would prevent my possible Mid marked down because on a single origin). Will try to find some data in Splunk related to past event that we had with a single origin failure. It didn't seem to affect other services in the catch all, but will need to double verify. I remember hitting @jrushf1239k about this. I'll I can say is I see this in the ATS debug logs which was in the catch all, there is a mention about the origin.
|
The "dest_domain=." line catches too much -- ATS maintains health on each line in parent.config separately, so there is potential to affect more delivery services when a single origin is slow. Traffic Ops should enumerate each origin into its own line in parent.config
The text was updated successfully, but these errors were encountered: