elek commented on pull request #2401:
URL: https://github.com/apache/ozone/pull/2401#issuecomment-880020034
Some notes about our offline discussion. The proposed behavior:
1. client doesn't set any replication information in `openKey` by default
2. if set explicitly in `ozone-site.xml` (client-side default!) or in ozone
sh argument it will be sent in the request
server side:
1. if key request contains replication info --> use it
2. if not, but bucket contains bucket level default (introduced by this
patch) --> use that
3. if not, use the cluster level server-side (!) default (might be
different from the client level default)
when bucket is created:
1. do not save any default one (unless specified with ozone sh)
S3g:
1. always use the map from storage class to replication config (expliclty
set the replication for all the new keys)
ofs/o3fs:
* client by default doesn't send any replication info --> see above
* administrator can create bucket with EC default: --> all the keys
created by users in that bucket will be EC encoded
* administrator can change server side default: --> all the new keys in
all the buckets will be EC encoded
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
