23 Oct
2025
23 Oct
'25
8:20 p.m.
Once upon a time, Jay R. Ashworth <jra@baylink.com> said:
It sounds like there should be a timestamp on every plan the Planner makes, and that should be carried all the way through to Route53 -- the *actual* root cause was that the actual installation of those delayed (and now older) records was permitted to happen, even though newer data was already installed, IME.
It sounds more like a lack of locking than a race condition. If 123 has to be processed before 456, then you need to take a lock to ensure that processing of 456 cannot begin before processing of 123 has completed. Out-of-order processing just because something took longer than expected is not the definition of a race condition. -- Chris Adams <cma@cmadams.net>