rawlinp commented on issue #4982:
URL: https://github.com/apache/trafficcontrol/issues/4982#issuecomment-878583835
Rather than adding a new endpoint, would it make sense to just add `type`
and `profile` query parameters to the existing `/cdns/{id}/queue_update`
endpoint? I think most of the time you're queuing within a single CDN, so it
might make sense to keep it CDN-specific, but within that CDN you can narrow
down by server type and profile.
I would prefer us to move away from having to do targeted queues in the
first place -- in general if you queue updates on a server that doesn't
actually have updates, it should be a no-op. The problem is that it adds load
on Traffic Ops to serve requests from `t3c` when they're not actually needed.
However, we are trying to get to a point where Traffic Ops can easily handle
the load from thousands of `t3c` instances at a time, so eventually we should
be able to just queue entire CDNs at a time and have the change fully
propagated in a few minutes rather than an hour.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
