Re: [ceph-users] no rebalance when changing chooseleaf_vary_r tunable

2018-04-04 Thread Adrian
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

Re: [ceph-users] no rebalance when changing chooseleaf_vary_r tunable

2018-04-04 Thread Gregory Farnum
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

[ceph-users] no rebalance when changing chooseleaf_vary_r tunable

2018-04-04 Thread Adrian
Hi all, Was wondering if someone could enlighten me... I've recently been upgrading a small test clusters tunables from bobtail to firefly prior to doing the same with an old production cluster. OS is rhel 7.4, kernel in test is all 3.10.0-693.el7.x86_64, in prod admin box is