Home
6.0 Administration
This section describes how to manage the nodes and services that make up a cluster.
Administrator's Reference
This section contains in-depth reference information for the administrator.
MapR Environment
This section provides information associated with the MapR environment.
Environment Variables
Describes the environment variables specific to MapR.
About env_override.sh

MapR 6.0 Documentation

6.0 Administration
This section describes how to manage the nodes and services that make up a cluster.
- Administering Users and Clusters
- Administering Nodes
- Administering Volumes
  This section provide information about how to organize and manage data using volumes, a unique feature of MapR clusters.
- Administering Files and Directories
- Administering Tables
  Administration of the MapR-DB is done primarily via the command line (maprcli) or with the MapR Control System (MCS). Regardless of whether the MapR-DB table is used for binary files or JSON documents, the same types of commands are used with slightly different parameter options. MapR-DB administration is associated with tables, columns and column families, and table regions.
- Administering Streams
- Administering MapR Gateways
  A MapR gateway mediates one-way communication between a source MapR cluster and a destination cluster. You can replicate MapR-DB tables (binary and JSON) and MapR-ES streams. MapR gateways also apply updates from JSON tables to their secondary indexes and propagate Change Data Capture (CDC) logs.
- Administering Services
- Monitoring the Cluster
  This section describes how to monitor the health and performance of a MapR cluster.
- Configuring Security
  Describes how to configure MapR security and manage secure clusters.
- Managing Secure Clusters
  Provides procedures that will enable you to use MapR clusters securely.
- Administering the MapR Data Access Gateway
  The MapR Data Access Gateway is a service that acts as a proxy and gateway for translating requests between lightweight client applications and the MapR cluster. This section describes considerations when upgrading the service, how to modify configuration settings, and how to administer and manage the service.
- Planning for High Availability
- Administrator's Reference
  This section contains in-depth reference information for the administrator.
  - maprcli and REST API Syntax
    This section provides information about the MapR command API. Most commands can be run on the command-line interface (CLI), or by making REST requests programmatically or in a browser.
  - Utilities
    This section contains information about various scripts and utilities.
  - Configuration Files
    This section contains reference information about various configuration files.
  - Alarms Reference
    The pages in this section provide details about all of the types of alarms.
  - MapR Environment
    This section provides information associated with the MapR environment.
    - MapR Parameters
    - Default MapR Configurations
    - Environment Variables
      Describes the environment variables specific to MapR.
      - About env_override.sh
    - Ports Used by MapR
    - Log Files
    - Cluster Maintenance Schedule
    - Language Support for MapR-DB Tables
      This section lists the human languages that MapR-DB tables can store, retrieve, and process.
- Troubleshooting Cluster Administration
- Best Practices for Backing Up MapR Information

About env_override.sh

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

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

env_override.sh is not removed or modified during an upgrade. /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.

Sample env_override.sh File

export CLDB_EXTERNAL_RPC_PORT=5000
export JAVA_HOME=/usr/lib/jvm/java-7-sun
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*