jhg03a commented on a change in pull request #4537: Add blueprint for Flexible Topologies URL: https://github.com/apache/trafficcontrol/pull/4537#discussion_r403348854
########## File path: blueprints/flexible-topologies.md ########## @@ -405,6 +405,8 @@ Once all Delivery Services have been migrated to Topologies, CDN operators will Troubleshooting issues with Delivery Services on the CDN may become slightly more difficult due to the fact that you will no longer be able to assume that any given Delivery Service will follow the same global hierarchy. Unique Topologies will provide unique paths through the CDN from client to origin, so an operator now needs to look up what the path *should be* based on the Delivery Service's Topology in order to triage issues along the delivery path. This may necessitate the development of Topology-based troubleshooting tools and visualizations. +As something to be aware of, content revalidations (via `regex_revalidate.config`) may take longer to propagate through a Topology the more tiers that it has, due to the nature of how ORT waits to revalidate until its cache's parents no longer have revalidations pending. Review comment: This is actually a big problem if you have revalidations coming in faster than they can chain through your topology since it's a global state on the server object. I also don't know how any of that would work if you have multiple topologies for a given server with different parentages. ---------------------------------------------------------------- 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
