----- Original Message -----
From: "Chris Adams via Outages-discussion" <outages-discussion@outages.org>
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.
Well, they said race, not me. But I think it's *kinda* a race -- this isn't locking per se, as I understand their writeup, you don't really know how *many* bad trx might be in flight, you just know you should trash (probably with a warning) any that come in out-of-order, right? Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274