-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Support variable server pools #11256
Support variable server pools #11256
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be updated too I suppose: https://github.com/minio/minio/tree/master/docs/erasure#what-is-erasure-code
886cd8c
to
ab00f17
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM per testing
ab00f17
to
bbfcad7
Compare
Current implementation requires server pools to have same erasure stripe sizes, to facilitate same SLA and expectations. This PR allows server pools to be variadic, i.e they do not have to be same erasure stripe sizes - instead they should have SLA for parity ratio. If the parity ratio cannot be guaranteed by the new server pool, the deployment is rejected i.e server pool expansion is not allowed.
bbfcad7
to
d7c9030
Compare
Mint Automation
11256-d7c9030/mint-gateway-azure.sh.log:
11256-d7c9030/mint-large-bucket.sh.log:
Deleting image on docker hub |
Description
Support variable server pools
Motivation and Context
The current implementation requires server pools to have
same erasure stripe sizes, to facilitate same SLA
and expectations.
This PR allows server pools to be variadic, i.e they
do not have to be same erasure stripe sizes - instead
they should have SLA for parity ratio.
If the parity ratio cannot be guaranteed by the new
server pool, the deployment is rejected i.e server
pool expansion is not allowed.
How to test this PR?
Test with the following example
Types of changes
Checklist:
commit-id
orPR #
here)