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.
  - Managing Data with Volumes
    Provides an overview of how to manage volume data.
    - Viewing the List of Volumes
      Explains how to view the list of volumes either through the Control Panel or the CLI.
    - Creating a Volume
      Describes volume types, and illustrates how to create volumes using either the Control System, CLI, or the REST API.
    - Viewing Volume Information
      Describes how to view volume information using either the Control System or the CLI.
    - Removing Volumes
      Explains how to remove a volume using either the Control System or the CLI.
    - Modifying Multiple Volumes
      Explains how to modify volumes using either the Control System or the CLI.
    - Modifying a Volume
      Describes how to edit a volume using either the Control System or the CLI.
    - Renaming a Volume
      Describes how to rename a volume using the Control System, CLI or the REST API.
    - Specifying Volume Inheritance Using the CLI
      Lists volume properties that can be inherited from other volumes.
    - Setting Data ACEs
      Describes how to set ACEs using both the GUI and the CLI.
    - Changing or Setting Mount Information for a Volume
      Describes how to set the mount path for a volume using either the Control System, the CLI, or the REST API.
    - Changing Volume Type
    - Selecting a Replication Type for High Availability
      Describes replication types for high-availability clusters, and the tradeoffs of using them.
    - Setting Quota for a Volume
      Describes how to set disk quotas for a volume using either the Control System, the CLI or the REST API.
    - Migrating a Volume off a Node Using the CLI
    - Setting Up Volume Topology
      Specifies how to use volume topology to place volumes on specific racks, nodes, or groups of nodes.
    - Viewing Active Volume Alarms
      Describes how to view volume alarms using the Control System and the CLI.
    - Working with Mirror Volumes
    - Enabling and Restricting Access to Tenant Volume and Data
      Describes how to restrict access to tenant volumes in a multi-tenant environment.
    - Working with Tiered Volumes
      - Erasure Coding Scheme for Data Protection and Recovery
        Describes the erasure coding (EC) schemes for data protection and recovery.
      - Specifying a Schedule for Offloading Data
        Explains how to create a schedule for automatic offloading of data, using the Control System, the CLI and the REST API.
      - Creating a Tiering-Enabled Volume
      - Associating a Tier, Tiering Rule, and/or Schedule with a Volume
      - Determining if a Volume is Enabled for Tiering
      - Offloading a Volume to a Tier
        Explains how to offload a volume to a tier using either the Control System, the CLI, or the REST API.
      - Recalling a Volume to MapR File System
        Explains how to recall offloaded data to the file system.
      - Viewing the List of Running Jobs
      - Terminating a Running Volume-Level Tiering Job
        Describes how to terminate a volume-level tiering job using either the Control System or the CLI.
      - Retrying Failed Operation
      - Running the Compactor Using the CLI and REST API
      - Retrieving the Status of a Volume-level Tiering Operation
      - Retrieving Tiering Statistics Using guts
        Explains how to use the guts utility to retrieve tiering statistics.
      - Moving back end Volume from the Command Line
    - Using Volume Links for Read and Write Operations
  - Managing Snapshots
    This section provide information about managing snapshots.
  - Managing User Disk Usage
  - Managing Schedules
  - Managing Tiers
  - Managing Storage Policies
- 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.

Moving back end Volume from the Command Line

This section contains information on migrating the following volumes to a different topology:

Metadata volume, which stores the DB tables for the metadata associated with the tier.
Erasure-coded volume, which stores the erasure-coded data.

Moving Metadata Volume to Another Topology

By default, the volume, which stores the DB tables for the metadata associated with the tier, is created in /var/mapr/tier/mapr.internal.tier.<volName> and is in the /data topology. However, you can move the metadata volume to another topology using the volume move command. For example:

/opt/mapr/bin/maprcli volume move -name <metadataVolName> -topology <newTopo>

curl -k -X POST 'https://<host>:8443/volume/move?name=<metadataVolName>&topology=<newTopo>' --user mapr:mapr

Moving Erasure-Coded Volume to Another Topology

The erasure-coded volume is by default created in the same topology as the front-end volume. You can specify a different topology for the erasure-coded volume when creating a front-end volume. You can also move the erasure coded volume to a different topology using the volume move command. For example:

/opt/mapr/bin/maprcli volume move -name <volName> -ectopology <newTopo>

curl -k -X POST 'https://<host>:8443/volume/move?name=<volName>&ectopology=<newTopo>' --user mapr:mapr

Here, the name parameter takes the name of the front-end volume and the ectopology parameter takes the topology to which to move the erasure-coded volume associated with the front-end volume. For more information, see volume move.