If you're running 100% coverage with dispersion report, then running it once per day seems reasonable.
If you're running something smaller, like 1-10%, then doing it once per hour might be reasonable. The point is, make it automatic and integrate it into your normal ops metrics. Track it over time and adjust as needed. --John On 12 Jan 2017, at 18:06, Mark Kirkwood wrote: > We are running a 2 region Swift cluster with write affinity. > > I've just managed to deceive myself with the Dispersion report :-( . The last > run of the populate was Early Dec, and the corresponding report happily shows > 100%. All good - seemingly. > > However probing the actual distribution of a number of objects created later > in Dec I see they have 3 copies in region 1 and 0 in regions 2. Hmm... I'm > guessing that if we ran the population more frequently this would have been > highlighted sooner. This begs the question - how frequently is it sensible to > run the populate? > > regards > > Mark > > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
