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.
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.
- Application Development Process
  Before you start developing applications on the MapR Data Platform platform, consider how you will get the data into the platform, the storage format of the data, the type of processing or modeling that is required, and how the data will be accessed.
- MapR XD and Apps
  The following sections provide information about accessing the MapR XD with C and Java applications.
- MapR Database and Apps
  This section contains information about developing client applications for JSON and key-value tables.
- MapR Event Store For Apache Kafka and Apps
  MapR Event Store For Apache Kafka brings integrated publish and subscribe messaging to MapR Data Platform.
- MapReduce and Apps
  This section contains information associated with developing YARN applications.
- MapR Data Science Refinery
  The MapR Data Science Refinery product is an easy-to-deploy and scalable data science toolkit with native access to all platform assets and superior out-of-the-box security.
- MapR Data Fabric for Kubernetes
  This section describes how to leverage the capabilities of the MapR Data Fabric for Kubernetes.
- Ecosystem Components
  The following sections provide information about each open-source project that is supported by the MapR Data Platform.
  - Ezmeral Ecosystem Packs
  - AsyncHBase
  - Cascading
  - Apache Drill
  - Flume
  - HBase
  - HBase Client and MapR Database Binary Tables
  - HCatalog
  - Hive
  - HttpFS
  - Hue
  - Impala
  - Livy
    Apache Livy is primarily used to provide integration between Hue and Spark.
  - MapR Event Store For Apache Kafka Clients and Tools
    Describes the supported MapR Event Store For Apache Kafka tools and clients.
  - S3 Gateway
    The S3 gateway is a service that provides an S3-compatible interface to expose data in MapR Data Platform as objects. The S3 gateway manages all inbound S3 API requests to put data into and get data out of cloud storage.
  - Myriad
    - Configure Myriad
      - Configuring Mesos-DNS
      - Configuring Services
        Services, such as JobHistoryServer, can be launched as a task from the Myriad Framework.
      - Configuring Multiple YARN Clusters
        This topic describes how to set up multiple Myriad frameworks and multiple YARN clusters in the Mesos environment.
      - Configuring Multiple YARN Clusters (Binary)
        This topic describes how to set up multiple Myriad frameworks and multiple YARN clusters in the Mesos environment for binary distribution.
      - Using a Different Scheduler
        Myriad uses MyriadFairScheduler by default. However, MyriadCapacityScheduler and MyriadFifoScheduler can also be used to run jobs.
    - Use Myriad
    - Myriad REST API
    - Troubleshoot Myriad
      Explains how to troubleshoot Myriad.
  - Oozie
  - Pig
  - Sentry
  - Apache Spark
  - Sqoop
  - YARN
  - Zeppelin
- Maven and MapR
  This section discusses topics associated with Maven and MapR.
- Developer's Reference
  This section contains in-depth information for the developer.
- API Documentation
  MapR Data Platform supports public APIs for MapR File System, MapR Database, and MapR Event Store For Apache Kafka. These APIs are available for application-development purposes.
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.

Using a Different Scheduler

Myriad uses MyriadFairScheduler by default. However, MyriadCapacityScheduler and MyriadFifoScheduler can also be used to run jobs.

About this task

IMPORTANT This component is deprecated. Hewlett Packard Enterprise recommends using an alternate product. For more information, see Discontinued Ecosystem Components.

The Myriad Scheduler property is set in the yarn-site.xml file:

<property>
  <name>yarn.resourcemanager.scheduler.class</name>
  <value>org.apache.myriad.scheduler.yarn.MyriadFairScheduler</value>
  <description>You can configure other schedulers from following list: 
     org.apache.myriad.scheduler.yarn.MyriadCapacityScheduler, 
     org.apache.myriad.scheduler.yarn.MyriadFifoScheduler</description>
</property>

IMPORTANT Fine-grained scaling only works with a MyriadFairScheduler configuration.

To use either MyriadCapacityScheduler or MyriadFifoScheduler:

Procedure

Edit the /opt/mapr/hadoop/hadoop-2.7.0/etc/hadoop/yarn-site.xml file.
For the yarn.resourcemanager.scheduler.class property, specify either org.apache.myriad.scheduler.yarn.MyriadCapacityScheduler or org.apache.myriad.scheduler.yarn.MyriadFifoScheduler
Modify the YARN scheduler minimum allocation properties.
The configure.sh sets these properties to zero (0) by default. When using a different scheduler, the properties must be set (as a minimum) to the following values:
```
yarn.scheduler.minimum-allocation-mb = 1024
yarn.scheduler.minimum-allocation-vcores = 1
yarn.scheduler.minimum-allocation-disks = 0
                
```
Copy or update the yarn-site.xml file on every node in the cluster.
Restart the initial Resource Manager from Marathon.