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
- Administrator's Reference
  This section contains in-depth reference information for the administrator.
  - maprcli and REST API Syntax
    This section provides information about the MapR command API. Most commands can be run on the command-line interface (CLI), or by making REST requests programmatically or in a browser.
  - Utilities
    Contains information about various scripts and utilities, that help setup, maintain, and monitor clusters.
  - Configuration Files
    This section contains reference information about various configuration files.
  - Alarms Reference
    The pages in this section provide details about all of the types of alarms.
    - User/Group Alarms
    - Cluster Alarms
    - Node Alarms
      - CLDB Service Alarm
      - Core Present Alarm
      - Debug Logging Active
      - Disk Failure
      - Duplicate Host ID
      - FileServer Service Alarm
      - Heartbeat Processing Slow
      - HBMaster Service Alarm
      - HBRegion Service Alarm
      - High MAST Gateway Memory Alarm
      - HistoryServer Alarm
      - HiveMeta Alarm
      - HiveServer 2 Alarm
      - Hoststats Alarm
      - Incorrect Topology Alarm
      - Installation Directory Full Alarm
      - Instance Mismatch Alarm
      - High FileServer Memory Alarm
      - MapR User Mismatch
      - Memory Allocation Alarm
      - Memory Usage Alarm
      - NFS Gateway Alarm
      - NFSv4 Service Alarm
      - NodeManager Alarm
        Explains how to resolve the issue with the Node Manager service stopping on the node.
      - No Disk Attached Alarm
      - No Heartbeat Alarm
        Describes the NODE_ALARM_NO_HEARTBEAT alarm.
      - Security Certificate Expiry Alarm
        Describes the NODE_ALARM_CERTIFICATE_NEAR_EXPIRATION alarm.
      - Node Too Many Containers
      - Oozie Alarm
      - PAM Misconfigured Alarm
      - ResourceManager Alarm
      - Root Partition Full Alarm
      - Tiny Buckets Flush Alarm
      - Time Skew Alarm
      - Version Alarm
      - WebServer Service Alarm
    - Table-Replication Alarms
    - Secondary Index Alarms
    - Volume Alarms
  - MapR Data Platform Environment
    This section provides information associated with the MapR Data Platform environment.
  - Sample JSON File for Metering
    A sample metering JSON file for an 8-node cluster with no workloads enabled.
  - Metering Data Descriptions
    This table lists the metrics collected by the metering feature.
- 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.

HistoryServer Alarm

UI Column

HistoryServer Alarm

Logged As

NODE_ALARM_SERVICE_HISTORYSERVER_DOWN

Meaning

The HistoryServer on the node has stopped running.

Resolution

Go to the node information page or the Services page in the Control System to check whether HistoryServer is running. Warden will try three times to restart the service automatically ever 30 minutes (by default). This 30 minute interval can be reconfigured using the parameter services.retryinterval.time.sec in the warden.conf file.

If warden successfully restarts the HistoryServer, the alarm is cleared. If Warden is unable to restart the HistoryServer, see more troubleshooting information.