About env_override.sh

Describes the purpose of the env_override.sh file.

The env_override.sh file allows you to create to store custom settings for environment variables. By default, /opt/mapr/conf/env.sh contains environment variables for a HPE Ezmeral Data Fabric cluster, but upgrading to a new Data Fabric release causes the env.sh file to be replaced. (A backup is stored as /opt/mapr/conf/env.sh<timestemp>.) After env.sh is replaced, any custom settings are removed.

For Data Fabric 6.0 and later, keep any custom settings in /opt/mapr/conf/env_override.sh. It is no longer necessary to modify env.sh.

Upgrading a cluster does not remove or modify env_override.sh. /opt/mapr/conf/env.sh reads the env_override.sh file at the end of its execution. If the same parameter is listed in both env.sh and env_override.sh, the value specified in env_override.sh is used. If env_override.sh is not present, the values in env.sh are used.

You create env_override.sh from a blank file and insert export statements into the file. For example:

Sample env_override.sh File

export CLDB_EXTERNAL_RPC_PORT=5000
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.8.10-0.el8_2.x86_64
export MAPR_HOME=/opt/mapr
export MAPR_EXTERNAL=10.10.123.25,10.10.123.30
export MAPR_SUBNETS=10.10.123.0/24,10.10.124.0/24
export MAPR_USER=mapr
export MAPR_ECOSYSTEM_LOGIN_OPTS=*hybrid*