Remove incorrect references to downtime on restart #429
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Build Instructions
Create a Python
venv
using 3.9 + and activate itRun
make stage