Ceph2

Ceph2

Сборник рецептов по ceph

Удаление OSD из кластера

If 226 is the number of the OSD to replace, node-130 is the name of the node and sdd is the name of the disk, then: 1. Mark this OSD out of the Ceph cluster: ceph osd out osd.226 2. Remove the failed OSD from the CRUSH map: ceph osd crush rm osd.226 3. Delete Ceph authentication keys for the OSD: ceph auth del osd.226 4. Remove the OSD from the Ceph cluster: ceph osd rm osd.226 Please keep in mind that whenever an OSD is unavailable your cluster health will not be OK, and it will continue to perform the recovery which is a normal Ceph operation in this situation. 5. So as long as the server is hot swappable which it should be, then just put the new drive in and perform the following tasks. If its node-130 then, keep in mind you will need to use the name of your node. ceph-deploy disk list node-130 6. Before adding the disk to the Ceph cluster, perform a disk zap: (Watch the output of the disk list for the location that gets assigned, that will be the location that you will run the osd create command on. For example if disk list output is [node-130][DEBUG ] /dev/sdd other, btrfs then disk zap will be the following: ceph-deploy disk zap node-130:sdd 7. Create an OSD on the disk, and Ceph will add it as osd.226: ceph-deploy --overwrite-conf osd create node-130:sdd Additional Information Once an OSD is created Ceph will run a recovery operation and start moving placement groups from secondary OSDs to the new OSD. Again the recovery operation will take a while depending on the size of your cluster, once it is completed your Ceph cluster will be HEALTH_OK.

When a new host or disk is added to a Ceph cluster, CRUSH starts a rebalancing operation, under which it moves the data from existing hosts/disks to a new host/ disk. Rebalancing is performed to keep all disks equally utilized, which improves the cluster performance and keeps it healthy. Internal Notes