Feature #433
closed
Added by Sage Weil over 13 years ago.
Updated almost 7 years ago.
Description
Currently the CRUSH weight is embedded in the CRUSH map. We need to either provide a way to feed this data in externally, or to automate the update of CRUSH map weights so that reweighting devices is less tedious.
- Target version changed from v0.23 to v0.24
- Estimated time set to 5:00 h
- Source set to 3
- Target version changed from v0.24 to v0.25
- Translation missing: en.field_position deleted (
372)
- Translation missing: en.field_position set to 2
- Translation missing: en.field_position deleted (
5)
- Translation missing: en.field_position set to 6
I think the thing to do here is extend the CrushWrapper interface (probably by wrapping something in mapper.c or builder.c) with functions to reweight a specific item in the tree, and then recalculate the ancestor weights accordinging. This is imperfect, as a given item can appear multiple times in the hierarchy, and maps deliberately allow parent weights to diverge from the sum of their children, but those situations don't come up for most users or use cases.
Then some monitor commands to actually do it.. 'osd crush reweight osd1 .5' or something along those lines. Maybe even one that spits out osd weights.
- Assignee set to Colin McCabe
- Status changed from New to Resolved
merged in commit:8aa4a9576857ce796fc9de1b0b9ae2144a830cb1
- Status changed from Resolved to New
Sage Weil wrote:
merged in commit:8aa4a9576857ce796fc9de1b0b9ae2144a830cb1
whoops, wrong bug, ignore that.
- Target version changed from v0.25 to 12
- Category set to 10
- Status changed from New to Resolved
- Assignee changed from Colin McCabe to Sage Weil
- Target version changed from 12 to v0.28
commit:4320cb15d4840c88b6e5c91c9923fb82749f78f4
- Project changed from Ceph to RADOS
- Category deleted (
10)
- Target version deleted (
v0.28)
Also available in: Atom
PDF