Agreed seems pretty useful.
Unsure exactly how it would be performed in some of the tooz backends,
but that's just a technical detail ;)
On 02/22/2016 03:41 PM, Chris Friesen wrote:
It may also be beneficial to take a page from POSIX "robust mutexes" and
introduce a way for the new lock holder to be notified that the previous
lock holder's lease expired rather than the lock being unlocked cleanly.
This alerts the new lock holder that the data protected by the lock may
be self-inconsistent since the old lock holder may have died while in
the middle of modifying things.
Chris
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
