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

Remove incorrect references to downtime on restart #429

Merged
merged 1 commit into from Mar 4, 2022

Conversation

ravindk89
Copy link
Collaborator

Summary

When I first wrote these docs I made some assumptions around the consequences of a restart.

After discussion with engineering, these sections are largely incorrect or misleading.

MinIO restarts are very fast - a few seconds long at most even for large clusters. Operations are atomic and strictly consistent. And S3 SDKs typically retry transparently. This means applications should not be aware at all of a restart assuming the admin is following best practices - namely simultaneous restart of all nodes/processes, no rolling restarts

Goals

  • [] Better describe how restarts effect ongoing operations
  • [] Remove incorrect warnings around downtime
  • [] Create checklist for upgrades to better frame the optimal setup

Build Instructions

Create a Python venv using 3.9 + and activate it

Run make stage

python -m venv venv
source venv bin activate
pip install -r requirements.txt
make stage

@ravindk89 ravindk89 merged commit 35d0c82 into master Mar 4, 2022
@ravindk89 ravindk89 deleted the minio-transparent-restarts branch March 22, 2022 23:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants