HPE Ezmeral Data Fabric 6.1.x is In Maintenance and transitions to "End of Maintenance" in June 2024. Please see the latest documentation.

About MapR 6.1
This site contains the main documentation for Version 6.1 of the MapR Converged Data Platform, including installation, configuration, administration, and reference information.
6.1 Installation
This section contains information about installing and upgrading MapR software. It also contains information about how to migrate data and applications from an Apache Hadoop cluster to a MapR cluster.
6.1 MapR Data Platform
MapR Data Platform is the industry-leading data platform for AI and analytics that solves enterprise business needs.
6.1 Administration
This section describes how to manage the nodes and services that make up a cluster.
- Administering Users and Clusters
  Lists topics that help manage a MapR cluster.
- Administering Nodes
  Provides a synopsis of managing nodes in a cluster.
- 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 Database is done primarily via the command line (maprcli) or with the Managed 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.
- 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 Database tables (binary and JSON) and MapR Event Store For Apache Kafka 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 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
  - CLDB Failover
    Explains the concept of CLDB failover, and its advantages.
  - Best Practices for Running a Highly Available Cluster
    Lists high availability cluster replication types, and the best practices for running such a cluster.
  - ResourceManager High Availability
    Provides an overview of how high availability for Resource Manager works.
- Administrator's Reference
  This section contains in-depth reference information for the administrator.
- Troubleshooting Cluster Administration
  Lists the common errors and their solutions.
- Best Practices for Backing Up MapR Information
  Lists the best practices and performance considerations to follow when backing up MapR information.
6.1 Development
This section contains information related to application development for Ezmeral ecosystem components and MapR Data Platform products, including the file system, Database (Key-Value and JSON), and Event Streams.
Other Docs
This section contains release-independent information, including: MapR Installer documentation, Ecosystem release notes, interoperability matrices, security vulnerabilities, and links to other MapR version documentation.
Glossary
Definitions for commonly used terms in MapR Converged Data Platform environments.

8. Restart All Nodes

To restart all nodes in the cluster, stop each node, configure the node with the new CLDB and ZooKeeper addresses, and start the node.

Complete the following steps on each node in the cluster:

Stop the node.
1. Change to the root user (or use sudo for the following commands).
2. Stop the Warden:
```
service mapr-warden stop
```

Configure all the nodes with the new CLDB and ZooKeeper addresses.

The script configure.sh configures a node to be part of a MapR cluster, or modifies services running on an existing node in the cluster. You must run this script to configure a node. The script creates (or updates) configuration files related to the cluster and the services running on the node.

Before you run configure.sh, make sure you have the hostname of the CLDB node and the hostnames of the ZooKeeper nodes. You can, optionally, specify the ports for the CLDB and ZooKeeper nodes as well. The default ports are:

Service	Default Port #
CLDB	7222
ZooKeeper	5181

The script configure.sh takes an optional cluster name and log file, the CLDB hostname, and comma-separated list of ZooKeeper host names or IP addresses (and optionally ports), using the following syntax:

/opt/mapr/server/configure.sh -C <host>[:<port>] -Z <host>[:<port>][,<host>[:<port>]...] [-L <logfile>][-N <cluster name>]

NOTE Each time you specify the -Z <host>[:<port>] option, you must use the same order for the ZooKeeper node list. If you change the order for any node, the ZooKeeper leader election process will fail.

Example:

/opt/mapr/server/configure.sh -C r1n1.sj.us:7222 -Z r1n1.sj.us:5181,r2n1.sj.us:5181,r3n1.sj.us:5181,r4n1.sj.us:5181,r5n1.sj.us:5181 -N MyCluster

Start Warden.
```
service mapr-warden start
```