This example assumes you are adding a new node to a cluster that is running the CLDB and ZooKeeper on three other nodes:
node_a,node_b,node_c. To configure a new node_d, which is not a CLDB or ZooKeeper node, run the following command:

Administration of the MapR Database is done primarily via the command line (maprcli) or with the MapR Control System (MCS). Regardless of whether the MapR Database table is used for binary files or JSON documents, the same types of commands are used with slightly different parameter
options. MapR Database 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.

Isolating CLDB Nodes

In a large cluster (100 nodes or more) create CLDB-only nodes to ensure high performance.
This configuration also provides additional control over the placement of the CLDB data,
for load balancing, fault tolerance, or high availability (HA). Setting up CLDB-only nodes
involves restricting the CLDB volume to its own topology and making sure all other volumes
are on a separate topology. Because both the CLDB-only path and the non-CLDB path are
children of the root topology path, new non-CLDB volumes are not guaranteed to keep off the
CLDB-only nodes. To avoid this problem, set a default volume topology. See Setting Default Volume Topology.