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.
  - Managing Nodes
    Describes the Nodes page on the Control System.
    - Viewing the list of Nodes
      Explains how to view the list of Nodes using either the Control System or the CLI.
    - Monitoring Nodes
      Explains how to monitor nodes using either the Control System or the CLI.
    - Viewing Node Details
      Describes how to view node details using either the Control System or the CLI.
    - Setting Up Node Topology
      Define node topologies for every node in the cluster.
    - Adding Nodes to a Cluster
      Describes how to add nodes to a cluster.
      - Isolating CLDB Nodes
        Lists the pros of creating CLDB-only nodes.
        Setting Up a CLDB-Only Node
        Describes how to setup a node for CLDB alone.
        Setting Up Volume Topology to Restrict the CLDB Volume to Specific Nodes
        Explains how to permit access to CLDB volumes only from specific nodes.
        Moving Volumes to a Separate Topology from the CLDB-Only Nodes
        Explains how to move non-CLDB volumes to a separate topology.
      - Isolating ZooKeeper Nodes
        Provides an overview on how to install a ZooKeeper-only node.
      - Configuration Example
        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, and node_c. To configure a new node_d, which is not a CLDB or ZooKeeper node, run the following command:
    - Removing Nodes from a Cluster
      Provides an overview of how to remove nodes from a cluster.
    - Reconfiguring a Node from the Command-Line
      Provides an overview of the procedure to reconfigure a node using the CLI.
    - Renaming a Node from the Command-Line
      Provides distribution-specific instructions for renaming a node.
    - Changing the IP Address of a Node
      Describes how to change the IP address of any node in the cluster using the CLI.
    - Viewing Active Node Alarms
      Describes how to view active node alarms using the Control System and the CLI.
    - Allocating Memory for Nodes
      Describes how the Warden allocates memory for nodes.
    - Performing Maintenance on a Node from the Command-Line
      Describes how to maintain the performance of a node using the CLI.
  - Managing Roles
    Describes how to manage roles on a node.
  - Managing Services
    Synopsis on managing services.
  - Managing Disks
    Provides a brief overview of adding and removing disks from the MapR file system.
- 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
- 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.

Isolating CLDB Nodes

Lists the pros of creating CLDB-only 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 that all other volumes are on a separate topology. As 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 Using the CLI.