Open Stack

On Thu, Mar 02 2017, gordon chung wrote:

> one of the issues we can't effectively partition the single bucket is 
> partly because we have multiple agents on a single bucket. in theory we 
> can use markers to partition the single bucket but because of multiple 
> workers, the marker has a very high chance of disappearing.
>
> in this case, only one agents is ever working on a bucket so it should 
> minimise the chance of a marker disappearing and therefore let us go 
> deeper into bucket.

Makes sense. So a consistent hashring of a few thousands of buckets
would solve that easily, as only one metricd will be assigned to a (lot
of) bucket(s).

That also means we may be able to get rid of the scheduler process?

-- 
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/20170302/f8d5121e/attachment.pgp>