Re: CRUSH depends on host + OSD?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mariusz,

> Usually removing OSD without removing host happens when you
> remove/replace dead drives.
> 
> Hosts are in map so
> 
> * CRUSH wont put 2 copies on same node
> * you can balance around network interface speed

That does not answer the original question IMO: "Why does the CRUSH map depend 
on hosts that no longer have OSDs on them?"

But I think it does answer the question "Why does the CRUSH map depend on OSDs 
AND hosts?"

> The question should be "why you remove all OSDs if you are going to
> remove host anyway" :)

This is your question, not mine!  :)
I am decommissioning the entire node.  What is the recommended (fastest yet 
safe) way of doing this?  I am currently follwing the current procedure

for all osdnum on server:
  ceph osd crush remove osd.osdnum

#wait for health to not be degraded, migration stops

for all osdnum on server:
  stop osdnum on server
  ceph auth del osd.osdnum
  ceph osd rm osdnum

# no new migration

# remove server with no OSD from CRUSH
ceph osd crush remove server
# lots of migration!

Thanks!
C.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux