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.

Configuring Secure Clusters for Running Commands Remotely

You can configure a number of secure clusters to access them all from one cluster.
This way, you need not log into each secure cluster separately and run
maprcli commands locally on them.

For example, suppose you need to manage two secure clusters, clusterA and clusterB.
One method of doing so would be to log into each cluster separately and run commands
locally on each. However, it is possible to log into clusterA only and manage both
clusters from clusterA, running commands locally for clusterA and remotely for
clusterB. When you type the maprcli commands, you would use the
-cluster parameter in those commands to specify which cluster you
want the commands to run on.

You can configure the secure clusters for remote access manually (as described below) or
automatically by running the configure-crosscluster.sh utility. If you
run the configure-crosscluster.sh utility, the utility configures the
clusters for running commands remotely in both directions. See configure-crosscluster.sh for more
information.

Setting Up Secure Clusters Manually for Cross-Cluster Access

To manually configure two secure clusters for remote access:

Log in to the secure cluster you want to run commands from.

In the rest of this procedure, this cluster is referred to as clusterA and the
remote cluster is referred to as clusterB.

Configure clusterA for communicating with the other clusters by editing
mapr-clusters.conf file on each node clusterA to specify the
hostname or IP address of the CLDB nodes on the other clusters.