SaketaChalamchala opened a new pull request, #5071:
URL: https://github.com/apache/ozone/pull/5071

   ## What changes were proposed in this pull request?
   
   The 
[documentation](https://ozone.apache.org/docs/1.3.0/start/runningviadocker.html)
 has instructions to create a single DN node Ozone docker environment. But, key 
create commands fail because server-side default replication config is RATIS 
THREE.
   We set client replication config to 1 in client configuration in the docker 
environments but, the client seems to accept custom replication configs only if 
passed as params on the CLI like `ozone sh key put /vol1/bucket1/key1 xxx -t 
RATIS -r ONE`.
   Updated the client to pick up custom replication config from CLI command 
params or client configuration before defaulting to server-side configs.
   Provided an option in docker compose to set replication type using env 
variable `OZONE_REPLICATION_TYPE` and updated the documentation to set 
replication type to RATIS, replication factor defaults in to 1 in docker 
compose file. This would ensure that users following the documentation would be 
able to spin up a single DN working Ozone cluster. 
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-8186
   
   ## How was this patch tested?
   
   Manual.
   Follow 
[documentation](https://ozone.apache.org/docs/1.3.0/start/runningviadocker.html)
 to spin up a docker cluster.
   Run
   ```
   ozone sh volume create /vol1
   ozone sh create bucket create /vol1/bucket1
   touch /tmp/myfile
   ozone sh key put /vol1/bucket1/key1 /tmp/myfile 
   ```
   


-- 
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]

Reply via email to