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.
- Planning the Cluster
  Describes information and factors used in planning your cluster.
  - Select Services
    This section describes some of the services that can be run on a node.
  - Cluster Design Objectives
    This section describes some of the work that your cluster performs, and identifies key design considerations.
  - Minimum Cluster Size
    All MapR production clusters must have a minimum of four data nodes except for HPE Ezmeral Data Fabric Edge.
  - Cluster Hardware
    Describes important hardware architecture considerations for your cluster.
  - Service Layout in a Cluster
    Provides an overview of segregating services on different nodes.
    - Node Types
      Depending on the size of your cluster, nodes may or may not perform specialized work.
    - Service Layout Guidelines for Large Clusters
      Describes how to install and segregate services on large clusters.
    - Service Layout Guidelines for Replication
      Based on the use case, replicating MapR Database tables and MapR Event Store For Apache Kafka may require the installation of MapR Gateways and the HBase client on one or more nodes.
    - MapR Monitoring Storage Options
      Describes various storage options for MapR Monitoring. The Control System relies on MapR monitoring components to display metrics, but can function without the monitoring components. Using MapR monitoring to store logs is optional.
    - Example Cluster Designs
      Describes how to design a MapR cluster for maximum availability, fault-tolerance, and performance.
    - Plan Initial Volumes
      Describes why it is important to define volumes.
  - Security Considerations
    Planning for security will help you identify security shortcomings and address them before you go into production.
  - User Accounts
    This section identifies how to organize authorized users of the cluster.
  - Next Step
    After you have a complete cluster plan, you are ready to prepare each node.
- Installing MapR and MapR Ecosystem Components
  Describes how to install MapR software and ecosystem components with or without the MapR Installer.
- Installing the File Migration Service on the Edge Cluster
  Describes how to install the File Migration service on CentOS nodes.
- Installing the MapR XD Distributed File and Object Store
  Describes how to install MapR XD software with or without the MapR Installer.
- Installing MapR Data Fabric for Kubernetes
  This section describes how to plan for and install the MapR Container Storage Interface (CSI) Storage Plugin and the MapR Data Fabric for Kubernetes FlexVolume Driver.
- Installing MapR in the Cloud
  Provides an overview of MapR cloud installer capabilities.
- Installing Metering
  This section describes how to install Metering by using the MapR Installer or manual steps.
- Upgrading MapR Core or EEP Components
  Depending on your current configuration, you may choose to upgrade the release version (core), ecosystem components, clients, or monitoring components.
- Setting Up Clients and Services
  Describes how to set up and use interfaces to an cluster from a client computer.
- Setting Up the Control System
  Describes how to configure and access the Control System.
- Migrating to MapR
  Provides instructions for migrating business-critical data and applications from an Apache Hadoop cluster to a MapR cluster.
- Applying a Patch
  You can apply a patch by using the MapR Installer, by using the command line (a manual process), or by using an Installer Stanza.
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.
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.

Service Layout Guidelines for Replication

Based on the use case, replicating MapR Database tables and MapR Event Store For Apache Kafka may require the installation of MapR Gateways and the HBase client on one or more nodes.

Guidelines for Installing Gateways

When you configure replication for MapR Database tables or MapR Event Store For Apache Kafka, MapR gateways provide one-way communication between a source MapR cluster and a destination cluster. It is recommended to install at least three gateways on the destination cluster. Installing two or more gateways on a destination cluster allows for replication failover in the event that one gateway is unavailable. Installing three gateways on a large cluster enables better throughput for data replication. Installing more than three gateways can improve availability but is not likely to improve replication performance.

Guidelines for Installing HBase Client

When you configure replication for MapR Database tables, the HBase client is not required by default. However, you must install the HBase client to replicate MapR Database tables in the following situations:

You plan to perform autosetup table replication using the MapR Database C API. In this case, you must install the HBase Client on the node where the C application will run.
You plan to perform autosetup table replication using the maprcli table replica autosetup command without direct copy. In this case, you must install the HBase Client on the node where you submit the maprcli table replica autosetup command. For more information about autosetup table replication, see Replica Autosetup for MapR Database Tables.