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
  - Managing Services
    Synopsis on managing services.
  - Setting Up Central Configuration from the Command-Line
    Describes the concept of a central location where customized MapR configuration files for MapR services are stored.
  - Viewing CLDB Information
    Describes how to view CLDB information from the CLDB page, and provides an explanation of each field that the page displays.
  - Managing Drill
    Provides a short description on managing Drill services.
  - Managing the MapR NFS Service
    Provides an overview of managing the NFS service on a licensed cluster.
    - Managing VIPs for NFS
      Explains how to use virtual IP addresses (VIPs) on NFS servers.
    - Accessing Data with NFS v3
      Describes how MapR works with NFS v3.
    - Accessing Data with NFS v4
      Describes how MapR works with the NFS v4 protocol. Presents an overview of the process flow to read and write MapR processes with NFS v4, and a list of NFS v4 features that MapR does not support.
    - Viewing the List of NFS Servers
      Explains how to view the list of NFS servers using the Control System.
    - Handling Heavy Write Loads on Red Hat Enterprise Linux
      Describes a fix to mitigate resource contention between NFS Clients and the NFS Server on Red Hat Linux.
    - Configure NFS Write Performance
      Describes how to set the optimal value for outstanding Remote Procedure Call (RPC) requests to the NFS server.
    - Adjusting NFS Memory Settings
    - Running NFS on a Non-standard Port
    - Enabling Debug Logging for NFS Using the CLI
    - Unmounting the MapR Cluster from the Command-Line
  - Managing MapR Data Platform POSIX Clients
    Provides a brief synopsis of MapR Data Platform POSIX clients.
  - Managing the MAST Gateway
  - Configuring NodeManager Restart
  - Managing Jobs and Applications
- 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.

Adjusting NFS Memory Settings

The memory allocated to each MapR service is specified in the /opt/mapr/conf/warden.conf file, which MapR automatically configures based on the physical memory available on the node. You can adjust the minimum and maximum memory used for NFS, as well as the percentage of the heap that it tries to use, by setting the percent, max, and min parameters in the warden.conf file on each NFS node. Example:

...
service.command.nfs.heapsize.percent=3
service.command.nfs.heapsize.max=1000
service.command.nfs.heapsize.min=64
...

The percentages need not add up to 100; in fact, you can use less than the full heap by setting the heapsize.percent parameters for all services to add up to less than 100% of the heap size. In general, you should not need to adjust the memory settings for individual services, unless you see specific memory-related problems occurring.