Hi Stefan, >>Only fyi i tested current hammer git master and got crashes / repeering pgs after just 5 hours of benchmarking. So be careful. Yes sure, I'll not upgrade until Hammer is released. (and maybe after first point release to be sure) Thanks for your reply. ----- Mail original ----- De: "Stefan Priebe" <s.priebe@xxxxxxxxxxxx> À: "aderumier" <aderumier@xxxxxxxxx> Envoyé: Lundi 9 Février 2015 07:13:07 Objet: Re: crush tunables : optimal : upgrade from firefly to hammer behaviour ? Only fyi i tested current hammer git master and got crashes / repeering pgs after just 5 hours of benchmarking. So be careful. crush optimal sets it to the current optimal value. So you need to upgrade your clients first and then set it to optimal again. Stefan Excuse my typo s ent from my mobile phone. Am 09.02.2015 um 06:32 schrieb Alexandre DERUMIER < aderumier@xxxxxxxxx >: Hi, I'm currently use crush tunables "optimal" value. If I upgrade from firefly to hammer, does the optimal value will upgrade to optimal values for hammer. So, does my clients (qemu-librbd) need to be also upgraded to hammer to support new hammer features ? If yes, I think to: - change crush tunables to firefly - upgrade firefly cluster to hammer cluster - upgrade all my clients to hammer. (with qemu live migration, to have new qemu process with last hammer librbd) - change crush tunables to hammer Is it the right way ? _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |