I think I did a bad job explaining my issue:
I have a fairly old cluster which had a crush map with two trees, one for
hdds and one for ssd, like root hdd {..} and root ssd {...} now with the
newer class based rules I used crushtool —reclassify to merge those two
trees into root default {...} So I already downloaded, edited and
Reuploaded the crush map, which resulted in a very minor data movement,
which crushtool —compare predicted. One of my pools is an ec pool with an
ec profile with crush-root=hdd. I can not, I think, change the ec-profile
of an existing pool. But since the pool runs on that profile, with the now
non existing crush-root=hdd, I am wondering if I can expect to run into
trouble down the line or does the cluster use some internal id, and the
string displayed only matters on creation. Basically am I safe or am I
hosed?
On Mon 18. May 2020 at 19:05, Eric Smith <Eric.Smith@xxxxxxxxxx> wrote:
> You'll probably have to decompile, hand edit, recompile, and reset the
> crush map pointing at the expected root. The EC profile is only used during
> pool creation and will not change the crush map if you change the EC
> profile. I think you can expect some data movement if you change the root
> but either way I would test it in a lab if you have one available.
>
> -----Original Message-----
> From: Dan <dan34567@xxxxxxxxx> On Behalf Of Dan
> Sent: Monday, May 18, 2020 9:14 AM
> To: ceph-users@xxxxxxx
> Subject: Dealing with non existing crush-root= after
> reclassify on ec pools
>
> I have reclassified a CRUSH map, using the crushtool to a class based
> ruleset.
> I still have an ec pool with an older ec profile with a new non existing
> crush-root=hdd
>
> I already switched the pool’s ruleset over to a newer rule with a newer
> ec-profile with a correct crush-root But pool ls detail still shows:
>
>
> pool 9 'data' erasure profile jerasure-3-1 size 4 min_size 3 …..
>
> Jerasure-3-1 being the old profile with non existing crush-root
>
> So what do I do now? Switching over the pool ruleset does not change the
> ec-profile, can I switch the ec-profile over?
> What can I expect having a pool with a ec-profile with a non existing
> crush-root key?
>
> Please advise.
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an
> email to ceph-users-leave@xxxxxxx
>
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
