On 28/04/17 03:48 AM, Julien Danjou wrote: > Yes, I wrote that in a review somewhere. We need to rework 1. so > deletion happens at the same time we lock the sack to process metrics > basically. We might want to merge the janitor into the worker I imagine. > Currently a janitor can grab metrics and do dumb things like: > - metric1 from sackA > - metric2 from sackB > - metric3 from sackA > > and do 3 different lock+delete -_-
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. -- gord __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
