On Tue, Nov 22, 2016 at 7:56 PM, Adrian Saul <[email protected]> wrote: > > Hi , > As part of migration between hardware I have been building new OSDs and > cleaning up old ones (osd rm osd.x, osd crush rm osd.x, auth del osd.x). > To try and prevent rebalancing kicking in until all the new OSDs are created > on a host I use "ceph osd set noin", however what I have seen is that if the > new OSD that is created uses a new unique ID, then the flag is honoured and > the OSD remains out until I bring it in. However if the OSD re-uses a > previous OSD id then it will go straight to in and start backfilling. I have > to manually out the OSD to stop it (or set nobackfill,norebalance). > > Am I doing something wrong in this process or is there something about "noin" > that is ignored for previously existing OSDs that have been removed from both > the OSD map and crush map?
There are a lot of different pieces of an OSD ID that need to get deleted for it to be truly gone; my guess is you've missed some of those. The noin flag doesn't prevent unlinked-but-up CRUSH entries from getting placed back into the tree, etc. We may also have a bug though, so if you can demonstrate that the ID doesn't exist in the CRUSH and OSD dumps then please create a ticket at tracker.ceph.com! -Greg _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
