Use maximum parity for config files (#11740)

Some deployments have low parity (EC:2), but we really do not need to
save our config data with the same parity configuration.

N/2 would be better to keep MinIO configurations intact when unexpected
a number of drives fail.
This commit is contained in:
Anis Elleuch
2021-03-09 19:19:47 +01:00
committed by GitHub
parent 57f3ed22d4
commit eac66e67ec
3 changed files with 12 additions and 5 deletions

View File

@@ -55,6 +55,10 @@ type ObjectOptions struct {
ProxyRequest bool // only set for GET/HEAD in active-active replication scenario
ProxyHeaderSet bool // only set for GET/HEAD in active-active replication scenario
ParentIsObject func(ctx context.Context, bucket, parent string) bool // Used to verify if parent is an object.
// Use the maximum parity (N/2), used when
// saving server configuration files
MaxParity bool
}
// BucketOptions represents bucket options for ObjectLayer bucket operations