[
https://issues.apache.org/jira/browse/HDDS-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-14486:
----------------------------------
Labels: pull-request-available (was: )
> [Website v2] [Docs] [Administrator Guide] Environment variables
> ---------------------------------------------------------------
>
> Key: HDDS-14486
> URL: https://issues.apache.org/jira/browse/HDDS-14486
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: documentation
> Reporter: Wei-Chiu Chuang
> Priority: Major
> Labels: pull-request-available
>
> Add a page in Administrator Guide -> Configuration -> Basic, after
> Configuration Files, to describe ozone-env.sh and environment variables.
> The ozone-env.sh is located at $OZONE_HOME/etc/hadoop. It defines the
> environment variables used by Ozone processes. There are a lot of environment
> variables, and the only required ones are `JAVA_HOME`.
> Some env variables may be applicable to all Ozone processes, such as
> JAVA_HOME, OZONE_HOME, OZONE_CONF_DIR, OZONE_LOG_DIR, OZONE_HEAPSIZE_MAX and
> OZONE_HEAPSIZE_MIN. Others may only apply to certain service. For example,
> OZONE_CLIENT_OPTS specifies Java properties for ozone commands and clients;
> similarly, OZONE_OM_OPTS for OM, OZONE_SCM_OPTS for SCM, OZONE_DATANODE_OPTS
> for Datanode, OZONE_S3G_OPTS for s3 gateway, OZONE_RECON_OPTS for Recon
> server.
> Instead of updating ozone-env.sh, create a system wide profile, say
> /etc/profile.d/ozone.sh. And then add the following as an example:
> ```
> export JAVA_HOME="$(/usr/libexec/java_home)"
> export OZONE_HOME=/opt/ozone
> export OZONE_CONF_DIR=/etc/ozone/conf
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
