Hi Wido,
Unexpected crush location changes can indeed be quite nasty.
With this in mind, I wonder if a crush lock would be useful.
ceph osd set nocrushchange
With that flag set, osds could still go in and out, but crush
move/add/remove/etc..., also tunables changes, would be blocked.
Thoughts?
-- Dan
On Mon, Oct 16, 2017 at 2:02 PM, Wido den Hollander <wido@xxxxxxxx> wrote:
> Hi,
>
> I completely overread this, but I just found out that osd_crush_location_hook was renamed to crush_location_hook in the new config style.
>
> When upgrading from Jewel to Luminous without touching your configuration OSDs will move to the default CRUSH location due to the hook not being executed.
>
> Was this an oversight with Luminous or was it intentional?
>
> Wido
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
