Yeah, I should have mentioned the swap-bucket option. We couldn't use
that because we actually didn't swap anything but moved the old hosts
to a different root and we keep them for erasure coding pools.
Zitat von Anthony D'Atri :
The strategy that Nghia described is inefficient for moving
The strategy that Nghia described is inefficient for moving data more than
once, but safe since there are always N copies, vs a strategy of setting noout,
destroying the OSDs, and recreating them on the new server. That would be more
efficient, albeit with a period of reduced redundancy.
I’ve
Hi,
I have a different approach in mind for a replacement, we successfully
accomplished that last year in our production environment where we
replaced all nodes of the cluster with newer hardware. Of course we
wanted to avoid rebalancing the data multiple times.
What we did was to create
