Understanding/Using Pools
Pages: 1 2
alienn
37 Posts
November 22, 2019, 9:09 amQuote from alienn on November 22, 2019, 9:09 amHmm... When I do the following:
cp crush-original-decompiled crush-original-decompiled-edited
nano crush-original-decompiled-edited # remove unsed rules
crushtool -c crush-original-decompiled-edited -o crush-original-decompiled-edited.bin # compile rule
crushtool -i crush-original-decompiled-edited.bin --reclassify --reclassify-root default hdd -o crush-new.bin # modify crushmap und change default class to hdd
crushtool -i crush-original --compare crush-new.bin # compare old and new crushmap
I get:
rule 0 had 0/10240 mismatched mappings (0)
rule 1 had 18432/18432 mismatched mappings (1)
rule 2 had 18432/18432 mismatched mappings (1)
rule 3 had 0/10240 mismatched mappings (0)
rule 4 had 10240/10240 mismatched mappings (1)
warning: maps are NOT equivalent
That seems to me that I will face a lot of data movement. Right? I would get the same (I think) when I just change the rule for the pool like this:
ceph osd pool set ceph-replicated-3 crush_rule by-host-hhd
Hmm... When I do the following:
cp crush-original-decompiled crush-original-decompiled-edited
nano crush-original-decompiled-edited # remove unsed rules
crushtool -c crush-original-decompiled-edited -o crush-original-decompiled-edited.bin # compile rule
crushtool -i crush-original-decompiled-edited.bin --reclassify --reclassify-root default hdd -o crush-new.bin # modify crushmap und change default class to hdd
crushtool -i crush-original --compare crush-new.bin # compare old and new crushmap
I get:
rule 0 had 0/10240 mismatched mappings (0)
rule 1 had 18432/18432 mismatched mappings (1)
rule 2 had 18432/18432 mismatched mappings (1)
rule 3 had 0/10240 mismatched mappings (0)
rule 4 had 10240/10240 mismatched mappings (1)
warning: maps are NOT equivalent
That seems to me that I will face a lot of data movement. Right? I would get the same (I think) when I just change the rule for the pool like this:
ceph osd pool set ceph-replicated-3 crush_rule by-host-hhd
admin
2,930 Posts
November 22, 2019, 9:26 amQuote from admin on November 22, 2019, 9:26 amas stated earlier, i understand you have only 1 current pool that uses default rule and wanted to change it to an hdd specific rule so you can add ssd pools afterwards.
if so then, as stated, remove the unused class specific rules you added before running the tool, and compare the tool output with the edited input not with the original one that had unused rules.
as stated earlier, i understand you have only 1 current pool that uses default rule and wanted to change it to an hdd specific rule so you can add ssd pools afterwards.
if so then, as stated, remove the unused class specific rules you added before running the tool, and compare the tool output with the edited input not with the original one that had unused rules.
Last edited on November 22, 2019, 9:26 am by admin · #12
Pages: 1 2
Understanding/Using Pools
alienn
37 Posts
Quote from alienn on November 22, 2019, 9:09 amHmm... When I do the following:
cp crush-original-decompiled crush-original-decompiled-edited nano crush-original-decompiled-edited # remove unsed rules crushtool -c crush-original-decompiled-edited -o crush-original-decompiled-edited.bin # compile rule crushtool -i crush-original-decompiled-edited.bin --reclassify --reclassify-root default hdd -o crush-new.bin # modify crushmap und change default class to hdd crushtool -i crush-original --compare crush-new.bin # compare old and new crushmapI get:
rule 0 had 0/10240 mismatched mappings (0) rule 1 had 18432/18432 mismatched mappings (1) rule 2 had 18432/18432 mismatched mappings (1) rule 3 had 0/10240 mismatched mappings (0) rule 4 had 10240/10240 mismatched mappings (1) warning: maps are NOT equivalentThat seems to me that I will face a lot of data movement. Right? I would get the same (I think) when I just change the rule for the pool like this:
ceph osd pool set ceph-replicated-3 crush_rule by-host-hhd
Hmm... When I do the following:
cp crush-original-decompiled crush-original-decompiled-edited nano crush-original-decompiled-edited # remove unsed rules crushtool -c crush-original-decompiled-edited -o crush-original-decompiled-edited.bin # compile rule crushtool -i crush-original-decompiled-edited.bin --reclassify --reclassify-root default hdd -o crush-new.bin # modify crushmap und change default class to hdd crushtool -i crush-original --compare crush-new.bin # compare old and new crushmap
I get:
rule 0 had 0/10240 mismatched mappings (0) rule 1 had 18432/18432 mismatched mappings (1) rule 2 had 18432/18432 mismatched mappings (1) rule 3 had 0/10240 mismatched mappings (0) rule 4 had 10240/10240 mismatched mappings (1) warning: maps are NOT equivalent
That seems to me that I will face a lot of data movement. Right? I would get the same (I think) when I just change the rule for the pool like this:
ceph osd pool set ceph-replicated-3 crush_rule by-host-hhd
admin
2,930 Posts
Quote from admin on November 22, 2019, 9:26 amas stated earlier, i understand you have only 1 current pool that uses default rule and wanted to change it to an hdd specific rule so you can add ssd pools afterwards.
if so then, as stated, remove the unused class specific rules you added before running the tool, and compare the tool output with the edited input not with the original one that had unused rules.
as stated earlier, i understand you have only 1 current pool that uses default rule and wanted to change it to an hdd specific rule so you can add ssd pools afterwards.
if so then, as stated, remove the unused class specific rules you added before running the tool, and compare the tool output with the edited input not with the original one that had unused rules.