adoroszlai commented on code in PR #4444: URL: https://github.com/apache/ozone/pull/4444#discussion_r1144339120
########## hadoop-ozone/dist/src/main/compose/ozone-ha/docker-config: ########## @@ -47,6 +48,7 @@ OZONE-SITE.XML_ozone.recon.db.dir=/data/metadata/recon OZONE-SITE.XML_ozone.recon.address=recon:9891 OZONE-SITE.XML_ozone.recon.http-address=0.0.0.0:9888 OZONE-SITE.XML_ozone.recon.https-address=0.0.0.0:9889 +OZONE-SITE.XML_dfs.container.ratis.datastream.enabled=true Review Comment: These are two separate settings. `dfs.container.ratis.datastream.enabled=true` enables it at the server-side, but it's up to the client to decide if it uses regular or streaming path. For FS API it is achieved by setting `ozone.fs.datastream.enabled`. ([docs](https://ci-hadoop.apache.org/view/Hadoop%20Ozone/job/ozone-doc-master/lastSuccessfulBuild/artifact/hadoop-hdds/docs/public/feature/streaming-write-pipeline.html)) In short, if we want to run `ozonefs.robot` in some compose environment, we need to add this config. It's just copied from the `ozone` and `ozonesecure` environments to the HA ones. -- 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]
