[openstack-dev] [gnocchi] per-sack vs per-metric locking tradeoffs
Julien Danjou
julien at danjou.info
Fri Apr 28 13:23:30 UTC 2017
On Fri, Apr 28 2017, gordon chung wrote:
> what if we just don't lock ever on delete, but if we still check lock to
> see if it's processed. at that point, the janitor knows that metric(s)
> is deleted, and since no one else is working on sack, any metricd that
> follows will also know that the metric(s) are deleted and therefore,
> won't work on it.
I did not understand your whole idea, can you detail a bit more?
Though the "check lock" approach usually does not work and is a source
of race condition, but again, I did not get the whole picture. :)
--
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170428/3ef9b9cd/attachment.sig>
More information about the OpenStack-dev
mailing list