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

Clarify effect of changing erasure coding parity #1365

Open
feorlen opened this issue Nov 11, 2024 · 0 comments
Open

Clarify effect of changing erasure coding parity #1365

feorlen opened this issue Nov 11, 2024 · 0 comments
Labels
tiny Small, bite-sized fixes that require minimal effort

Comments

@feorlen
Copy link
Collaborator

feorlen commented Nov 11, 2024

This admonition in operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst could be more forceful that changing parity doesn't automagically do anything to existing objects.

.. important::

   While you can change erasure parity settings at any time, objects written with a given parity do **not** automatically update to the new parity settings.

Some additions to consider:

Objects take the parity in effect at the time of the original write operation for the object.

Customer changed their parity and was hoping it would update cluster-wide. Maybe reword would make it more memorable next time somebody is in this situation. 🤞🏻

@feorlen feorlen added the tiny Small, bite-sized fixes that require minimal effort label Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tiny Small, bite-sized fixes that require minimal effort
Projects
None yet
Development

No branches or pull requests

1 participant