Hi Gregory
We were planning on going to chooseleaf_vary_r=4 so we could upgrade to
jewel now and schedule the change to 1 at a more suitable time since we
were expecting a large rebalancing of objects (should have mentioned that).
Good to know that there's a valid reason we didn't see any rebalan
http://docs.ceph.com/docs/master/rados/operations/crush-map/#firefly-crush-tunables3
"The optimal value (in terms of computational cost and correctness) is 1."
I think you're just finding that the production cluster, with a much
larger number of buckets, didn't ever run in to the situation
choose