Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

osd: check if osd is safe-to-destroy before removal #9230

Merged
merged 1 commit into from Nov 25, 2021
Merged

osd: check if osd is safe-to-destroy before removal #9230

merged 1 commit into from Nov 25, 2021

Commits on Nov 25, 2021

  1. osd: check if osd is ok-to-stop before removal 

    If multiple removal jobs are fired in parallel, there is a risk of
losing data since we will forcefully remove the OSD. It's also simply
true if a single OSD is not safe to destroy, there is also a risk of
data loss.

So now, we check if the OSD is safe-to-destroy first and then proceed.
The code waits forever and retries every minute unless the
--force-osd-removal flag is passed.

Signed-off-by: Sébastien Han <seb@redhat.com>
    @leseb
    leseb committed Nov 25, 2021
    Copy the full SHA
    7402c2c View commit details
    Browse the repository at this point in the history