Actions
Documentation #8322
closedmake "manually add OSD" documents to make CRUSH command needs clearer
% Done:
0%
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
https://ceph.com/docs/master/rados/operations/add-or-rm-osds/#adding-osds gives the following command for adding an OSD to the CRUSH map:
ceph osd crush add {id-or-name} {weight} [{bucket-type}={bucket-name} ...]</pre
This gives users the impression that all buckets are optional, but in any standard cluster configuration you must specify the "host" bucket or the OSD won't be used to store data. Make this clearer so it's less likely to be misused.
Updated by Greg Farnum almost 10 years ago
My text for the user who pointed this out:
The CRUSH add commands allow you to add OSDs wherever in the hierarchy you wish. This includes OSDs which are disconnected from the root, or OSDs in distinct hierarchies, or whatever. If you specify at least one bucket, the OSD will be placed in the most specific bucket you specify, *and* that bucket will be moved underneath the other buckets you specify. If you specify only the root bucket, the OSD will be directly attached to the root, but default rules expect OSDs to be inside of hosts and the CRUSH rules reflect that.
Updated by John Wilkins almost 10 years ago
- Status changed from New to In Progress
Updated by John Wilkins almost 10 years ago
- Status changed from In Progress to Resolved
Actions