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

fix: relax metadata checks for healing #19165

Merged
merged 1 commit into from Mar 1, 2024

Conversation

harshavardhana
Copy link
Member

@harshavardhana harshavardhana commented Feb 29, 2024

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

fix: relax metadata checks for healing

Motivation and Context

we should do this to ensure that we focus on
data healing as the primary requirement, fixing
metadata as part of healing must be done, but
making data available is the main focus.

the main reason is metadata inconsistencies can
cause data availability issues, which must be
avoided at all costs.

will be bringing in an additional healing mechanism
that involves "metadata-only" healing, for now we do
not expect to have these checks.

continuation of #19154

How to test this PR?

As per #19154

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

we should do this to ensure that we focus on
data healing as primary focus, fixing metadata
as part of healing must be done but making
data available is the main focus.

the main reason is metadata inconsistencies can
cause data availability issues, which must be
avoided at all cost.

will be bringing in an additional healing mechanism
that involves "metadata-only" heal, for now we do
not expect to have these checks.

continuation of minio#19154

Bonus: add a pro-active healthcheck to perform a connection
@harshavardhana harshavardhana merged commit c599c11 into minio:master Mar 1, 2024
20 checks passed
@harshavardhana harshavardhana deleted the relax-metadata branch March 1, 2024 06:49
kanagarajkm pushed a commit that referenced this pull request Mar 30, 2024
we should do this to ensure that we focus on
data healing as primary focus, fixing metadata
as part of healing must be done but making
data available is the main focus.

the main reason is metadata inconsistencies can
cause data availability issues, which must be
avoided at all cost.

will be bringing in an additional healing mechanism
that involves "metadata-only" heal, for now we do
not expect to have these checks.

continuation of #19154

Bonus: add a pro-active healthcheck to perform a connection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants