On Fri, Apr 28 2017, gordon chung wrote: > if the sack is unlocked, then it means a processing worker isn't looking > at the sack, and when it does lock the sack, it first has to check sack > for existing measures to process and then check indexer to validate that > they are still active. because it checks indexer later, even if both > janitor and processing worker check lock at same time, we can guarantee > it will have indexer state processing worker sees is > 00:00:00 since > janitor has state before getting lock, while processing worker as state > sometime after getting lock.
My brain hurts but that sounds perfect. That even means we potentially did not have to lock currently, sack or no sack. -- Julien Danjou // Free Software hacker // https://julien.danjou.info
signature.asc
Description: PGP signature
__________________________________________________________________________ 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
