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 */
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
