An out osd still has a crush weight. Removing that osd or weighting it to 0
will change the weight of the host that it's in. That is why data moves
again. There is a thread in the ML started by Sage about possible ways to
confront the double data shift when drives fail. Data moving of when it
goes out and then again when it is removed from the cluster.
If the drive was still readable when it was marked out, the best method is
to weight it to 0 while it is still running so it can be used to offload
its data. Also in this method, when you remove it from the cluster, there
will not be any additional data movement.
On Tue, Feb 13, 2018, 6:55 AM Christian Sarrasin <c.n...@cleansafecloud.com>
> Thanks for your input John! This doesn't really match the doc ,
> which suggests just taking them out and only using "reweight" in case of
> issues (with small clusters).
> Is "reweight" considered a must before removing and OSD?
> On 13/02/18 12:34, John Petrini wrote:
> > The rule of thumb is to reweight to 0 prior to marking out. This should
> > avoid causing data movement twice as you're experiencing.
> ceph-users mailing list
ceph-users mailing list