Currently, ORT uses the parent_pending flag in a TO endpoint to determine whether any parents of the current server have updates pending.
We should change ORT to calculate this itself. It has all the data to do so.
The calculation itself is logic (mostly SQL) performed on the data. Logic that becomes more complex with the move from DeliveryServiceServers to Topologies.
This is just one more thing that should be done in ORT because it can, and because ORT is canaryable, where the TO Monolith is not. Not a huge issue, but a code/canary/rollback improvement.
rob05c
commented
3 years ago
Currently, ORT uses the
parent_pendingflag in a TO endpoint to determine whether any parents of the current server have updates pending.We should change ORT to calculate this itself. It has all the data to do so.
The calculation itself is logic (mostly SQL) performed on the data. Logic that becomes more complex with the move from DeliveryServiceServers to Topologies.
This is just one more thing that should be done in ORT because it can, and because ORT is canaryable, where the TO Monolith is not. Not a huge issue, but a code/canary/rollback improvement.
I'm submitting a ...
Traffic Control components affected ...
Current behavior:
TO performs logic to determine parents pending, and TO requests that.
New behavior:
ORT performs logic to determine parents pending.
Minimal reproduction of the problem with instructions:
N/A. Behavior does not change.
Anything else: