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.

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

update() stale rebalance stats() object during pool expansion #18882

Merged
merged 1 commit into from
Jan 27, 2024

Conversation

harshavardhana
Copy link
Member

Community Contribution License

All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.

Description

update() stale rebalance stats() object during pool expansion

Motivation and Context

it is entirely possible that a rebalance process that was
running when it was asked to "stop" it failed to write its
last statistics to the disk.

After this, a pool expansion can cause disruption, and all
S3 API calls would fail at the IsPoolRebalancing() function.

This PR makes sure that we update rebalance.bin under
such conditions to avoid any runtime crashes.

How to test this PR?

You need to introduce situations of a bit of instability on
the cluster when rebalance fails to save its statistics.

There is a customer who seems to have faced this problem.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Optimization (provides speedup with no functional changes)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • Fixes a regression (If yes, please add commit-id or PR # here)
  • Unit tests added/updated
  • Internal documentation updated
  • Create a documentation update request here

it is entirely possible that a rebalance process which was running
when it was asked to "stop" it failed to write its last statistics
to the disk.

After this a pool expansion can cause disruption and all S3 API
calls would fail at IsPoolRebalancing() function.

This PRs makes sure that we update rebalance.bin under such
conditions to avoid any runtime crashes.
@harshavardhana harshavardhana merged commit 32e668e into minio:master Jan 27, 2024
20 checks passed
@harshavardhana harshavardhana deleted the fix-rebalance branch January 27, 2024 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants