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.

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.

Shutting Down a Cluster

Verify that MapReduce processes are not active, and that no data is being loaded to
the cluster or being persisted within the cluster.

When you shut down a cluster, follow this sequence to preserve your data and
replication:

Verify that recent data has finished processing.

Shut down any NFS servers.

Shut down any ecosystem components that are running.

Shut down ResourceManager and NodeManager services if you are using YARN

Shut down Warden on all nodes that are not running CLDB.

Shut down Warden on the CLDB nodes.

Shut down ZooKeeper on the ZooKeeper nodes.

Complete the following steps to shut down the cluster:

Change to the root user (or use sudo for the
following commands).

Before shutting down the cluster, you will need a list of NFS nodes, CLDB nodes,
and all remaining nodes. Once the CLDB is shut down, you cannot retrieve a list of
nodes; it is important to obtain this information at the beginning of the process.
Use the node
list command as follows:

If your cluster is running any ecosystem components, shut down those components on
all nodes.

Shut down all ResourceManager and NodeManager services on all nodes. To shut down
ResourceManager and NodeManager services specify the maprcli node
services command with the name parameter and either the
filter or the node parameter . Example: