Added by Tom Clegg over 1 year ago.
Updated about 1 month ago.
1 (0 open — 1 closed)
Use source:lib/controller/dblock module, see #18339.
This should be the kind of lock that allows the new process can elbow out the old process -- I'm thinking of the situation where we start a new "something" and want it to replace the old "something".
So we want to communicate:
On second thought, that might be a bad idea, because it could lead to two processes fighting over the lock instead of one getting it and the other failing.
The one that fails to get the lock, perhaps it could stay up health check reports it in a "failed to get lock" state? Also, can the lock record some information about the node that does have the lock.
When lock is acquired, record hostname + process id
18071-dblock-keep-balance-and-dispatch @ 15043a6825ecd62ccb2272025384474a235b30cc -- developer-run-tests: #3346
Just one small suggestion:
The rest LGTM
Applied in changeset arvados|4529d84afb3549ccb4ae9005a8f64f558c2bbe5c.
Also available in: Atom