This is the documentation for CDH 5.1.x. Documentation for other versions is available at Cloudera Documentation.

Configuring High Availability for ResourceManager (MRv2/YARN)

This guide provides an overview of YARN ResourceManager High Availability (RM HA), and explains how to configure and use this feature.

The ResourceManager (RM) is responsible for tracking the resources in a cluster and scheduling applications (for example, MapReduce jobs). Before CDH 5, the RM was a single point of failure in a YARN cluster. The High Availability feature adds redundancy in the form of an Active/Standby ResourceManager pair to remove this single point of failure. Furthermore, upon failover from the Standby ResourceManager to the Active, the applications can resume from their last check-pointed state; for example, completed map tasks in a MapReduce job are not re-run on a subsequent attempt. This allows events such the following to be handled without any significant performance effect on running applications.:
  • Unplanned events such as machine crashes
  • Planned maintenance events such as software or hardware upgrades on the machine running the ResourceManager.

Architecture

ResourceManager HA is implemented by means of an Active/Standby pair of ResourceManagers. On start-up, each RM is in the Standby state: the process is started, but the state is not loaded. When transitioning to active, the RM loads the internal state from the designated state store and starts all the internal services. The stimulus to transition-to-active comes from either the administrator (through the CLI) or through the integrated failover controller when automatic failover is enabled. The subsections that follow provide more details about the components of RM HA.

RM Restart

RM Restart allows restarting the RM, while recovering the in-flight applications if recovery is enabled. To achieve this, the RM stores its internal state, primarily application-related data and tokens, to the RMStateStore; the cluster resources are re-constructed when the NodeManagers connect. The available alternatives for the state store are MemoryRMStateStore (a memory-based implementation), FileSystemRMStateStore (file system-based implementation; HDFS can be used for the file system), and ZKRMStateStore (ZooKeeper-based implementation).

Fencing

When running two RMs, a split-brain situation can arise where both RMs assume they are Active. To avoid this, only a single RM should be able to perform Active operations and the other RM should be "fenced". The ZooKeeper-based state store (ZKRMStateStore) allows a single RM to make changes to the stored state, implicitly fencing the other RM. This is accomplished by the RM claiming exclusive create-delete permissions on the root znode. The ACLs on the root znode are automatically created based on the ACLs configured for the store; in case of secure clusters, Cloudera recommends that you set ACLs for the root node such that both RMs share read-write-admin access, but have exclusive create-delete access. The fencing is implicit and doesn't require explicit configuration (as fencing in HDFS and MRv1 does). You can plug in a custom "Fencer" if you choose to – for example, to use a different implementation of the state store.

Configuration and FailoverProxy

In an HA setting, you should configure two RMs to use different ports (for example, ports on different hosts). To facilitate this, YARN uses the notion of an RM Identifier (rm-id). Each RM has a unique rm-id, and all the RPC configurations (<rpc-address>; for example yarn.resourcemanager.address) for that RM can be configured via <rpc-address>.<rm-id>. Clients, ApplicationMasters, and NodeManagers use these RPC addresses to talk to the Active RM automatically, even after a failover. To achieve this, they cycle through the list of RMs in the configuration. This is done automatically and doesn't require any configuration (as in does in HDFS and MRv1).

Manual transitions and failover

You can use the command-line tool yarn rmadmin to transition a particular RM to Active or Standby state, to fail over from one RM to the other, to get the HA state of an RM, and to monitor an RM's health.

Automatic failover

By default, RM HA uses ZKFC (ZooKeeper-based failover controller) for automatic failover in case the Active RM is unreachable or goes down. Internally, the ActiveStandbyElector is used to elect the Active RM. The failover controller runs as part of the RM (not as a separate process as in HDFS and MapReduce v1) and requires no further setup after the appropriate properties are configured in yarn-site.xml.

You can plug in a custom failover controller if you prefer.

Setting up ResourceManager HA

To configure and start ResourceManager HA, proceed as follows:
  1. Stop all YARN daemons,
  2. Update the configuration used by the ResourceManagers, NodeManagers and clients
  3. Start all YARN daemons

Step 1: Stop the YARN daemons

To stop the YARN daemons:

Stop the MapReduce JobHistory service, ResourceManager service, and NodeManager on all nodes where they are running, as follows: 
$ sudo service hadoop-mapreduce-historyserver stop
$ sudo service hadoop-yarn-resourcemanager stop
$ sudo service hadoop-yarn-nodemanager stop

Step 2: Configure Manual Failover, and Optionally Automatic Failover

To configure failover:
  Note:

Configure the following properties in yarn-site.xml as shown, whether you are configuring manual or automatic failover. They are sufficient to configure manual failover. You need to configure additional properties for automatic failover.

Name Used On Default Value Recommended Value Description 
yarn.resourcemanager.
ha.enabled
 
ResourceManager,
NodeManager,
Client
 
false
 true Enable HA 
yarn.resourcemanager.
ha.rm-ids
 
ResourceManager,
NodeManager,
Client
 
(None)
 
Cluster-specific,
e.g., rm1,rm2

Comma-separated list of ResourceManager ids in this cluster.

 
yarn.resourcemanager.
ha.id
 
ResourceManager
 
(None)
 
RM-specific,
e.g., rm1
 Id of the current ResourceManager. Must be set explicitly on each ResourceManager to the appropriate value. 
yarn.resourcemanager.
address.<rm-id>
 
ResourceManager,
Client
 
(None)
 
Cluster-specific
 The value of yarn.resourcemanager. address (Client-RM RPC) for this RM. Must be set for all RMs. 
yarn.resourcemanager.
scheduler.address.<rm-id>
 
ResourceManager,
Client
 
(None)
 
Cluster-specific
 The value of yarn.resourcemanager. scheduler.address (AM-RM RPC) for this RM. Must beset for all RMs. 
yarn.resourcemanager.
admin.address.<rm-id>
 
ResourceManager,
Client/Admin
 
(None)
 
Cluster-specific
 The value of yarn.resourcemanager. admin.address (RM administration) for this RM. Must be set for all RMs. 
yarn.resourcemanager.
resource-tracker.address.
<rm-id>
 
ResourceManager,
NodeManager
 
(None)
 
Cluster-specific
 The value of yarn.resourcemanager. resource-tracker.address (NM-RM RPC) for this RM. Must be set for all RMs. 
yarn.resourcemanager.
webapp.address.<rm-id>
 
ResourceManager,
Client
 
(None)
 
Cluster-specific
 The value of yarn.resourcemanager. webapp.address (RM webapp) for this RM.Must be set for all RMs. 
yarn.resourcemanager.
recovery.enabled
 
ResourceManager
 
false
 
true
 Enable job recovery on RM restart or failover. 
yarn.resourcemanager.
store.class
 
ResourceManager
 
org.apache.hadoop.
yarn.server.
resourcemanager.
recovery.
FileSystemRMStateStore
 
org.apache.
hadoop.yarn.
server.
resourcemanager.
recovery.
ZKRMStateStore
 The RMStateStore implementation to use to store the ResourceManager's internal state. The ZooKeeper- based store supports fencing implicitly, i.e., allows a single ResourceManager to make multiple changes at a time, and hence is recommended. 
yarn.resourcemanager.
zk-address
 
ResourceManager
 
(None)
 
Cluster-
specific
 The ZooKeeper quorum to use to store the ResourceManager's internal state. 
yarn.resourcemanager.
zk-acl
 
ResourceManager
 
world:anyone:rwcda
 
Cluster-
specific
 The ACLs the ResourceManager uses for the znode structure to store the internal state. 
yarn.resourcemanager.zk-
state-store.root-node.acl
 
ResourceManager
 
(None)
 
Cluster-
specific
 The ACLs used for the root node of the ZooKeeper state store. The ACLs set here should allow both ResourceManagers to read, write, and administer, with exclusive access to create and delete. If nothing is specified, the root node ACLs are automatically generated on the basis of the ACLs specified through yarn.resourcemanager.zk-acl. But that leaves a security hole in a secure setup.

To configure automatic failover:

Configure the following additional properties in yarn-site.xml to configure automatic failover.

Name Used On Default Value Recommended Value Description 
yarn.resourcemanager.
ha.automatic-failover.enabled
 
ResourceManager
 
true
 true Enable automatic failover 
yarn.resourcemanager.
ha.automatic-failover.embedded
 
ResourceManager
 
true
 
true
 Use the EmbeddedElectorService to pick an Active RM from the ensemble 
yarn.resourcemanager.
cluster-id
 
ResourceManager
 No default value. 
Cluster-
specific
 Cluster name used by the ActiveStandbyElector to elect one of the ResourceManagers as leader.

The following is a sample yarn-site.xml showing these properties configured:

<configuration>
<!-- Resource Manager Configs -->
  <property>
    <name>yarn.resourcemanager.connect.retry-interval.ms</name>
    <value>2000</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.enabled</name>
    <value>true</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.automatic-failover.enabled</name>
    <value>true</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.automatic-failover.embedded</name>
    <value>true</value>
  </property>
  <property>
    <name>yarn.resourcemanager.cluster-id</name>
    <value>pseudo-yarn-rm-cluster</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.rm-ids</name>
    <value>rm1,rm2</value>
  </property>
  <property>
    <name>yarn.resourcemanager.ha.id</name>
    <value>rm1</value>
  </property>
  <property>
    <name>yarn.resourcemanager.scheduler.class</name>
    <value>org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler</value>
  </property>
  <property>
    <name>yarn.resourcemanager.recovery.enabled</name>
    <value>true</value>
  </property>
  <property>
    <name>yarn.resourcemanager.store.class</name>
    <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore</value>
  </property>
  <property>
    <name>yarn.resourcemanager.zk.state-store.address</name>
    <value>localhost:2181</value>
  </property>
  <property>
    <name>yarn.app.mapreduce.am.scheduler.connection.wait.interval-ms</name>
    <value>5000</value>
  </property>

  <!-- RM1 configs -->
  <property>
    <name>yarn.resourcemanager.address.rm1</name>
    <value>host1:23140</value>
  </property>
  <property>
    <name>yarn.resourcemanager.scheduler.address.rm1</name>
    <value>host1:23130</value>
  </property>
  <property>
    <name>yarn.resourcemanager.webapp.https.address.rm1</name>
    <value>host1:23189</value>
  </property>
  <property>
    <name>yarn.resourcemanager.webapp.address.rm1</name>
    <value>host1:23188</value>
  </property>
  <property>
    <name>yarn.resourcemanager.resource-tracker.address.rm1</name>
    <value>host1:23125</value>
  </property>
  <property>
    <name>yarn.resourcemanager.admin.address.rm1</name>
    <value>host1:23141</value>
  </property>

  <!-- RM2 configs -->
  <property>
    <name>yarn.resourcemanager.address.rm2</name>
    <value>host2:23140</value>
  </property>
  <property>
    <name>yarn.resourcemanager.scheduler.address.rm2</name>
    <value>host2:23130</value>
  </property>
  <property>
    <name>yarn.resourcemanager.webapp.https.address.rm2</name>
    <value>host2:23189</value>
  </property>
  <property>
    <name>yarn.resourcemanager.webapp.address.rm2</name>
    <value>host2:23188</value>
  </property>
  <property>
    <name>yarn.resourcemanager.resource-tracker.address.rm2</name>
    <value>host2:23125</value>
  </property>
  <property>
    <name>yarn.resourcemanager.admin.address.rm2</name>
    <value>host2:23141</value>
  </property>

<!-- Node Manager Configs -->
  <property>
    <description>Address where the localizer IPC is.</description>
    <name>yarn.nodemanager.localizer.address</name>
    <value>0.0.0.0:23344</value>
  </property>
  <property>
    <description>NM Webapp address.</description>
    <name>yarn.nodemanager.webapp.address</name>
    <value>0.0.0.0:23999</value>
  </property>
  <property>
    <name>yarn.nodemanager.aux-services</name>
    <value>mapreduce_shuffle</value>
  </property>
  <property>
    <name>yarn.nodemanager.local-dirs</name>
    <value>/tmp/pseudo-dist/yarn/local</value>
  </property>
  <property>
    <name>yarn.nodemanager.log-dirs</name>
    <value>/tmp/pseudo-dist/yarn/log</value>
  </property>
  <property>
    <name>mapreduce.shuffle.port</name>
    <value>23080</value>
  </property>
</configuration>

Step 3: Re-start the YARN daemons

To re-start the YARN daemons:

Start the MapReduce JobHistory server, ResourceManager, and NodeManager on all nodes where they were previously running, as follows: 
$ sudo service hadoop-mapreduce-historyserver start
$ sudo service hadoop-yarn-resourcemanager start
$ sudo service hadoop-yarn-nodemanager start

Using yarn rmadmin to Administer ResourceManager HA

You can use yarn rmadmin on the command line to manage your ResourceManager HA deployment. yarn rmadmin has the following options related to RM HA:
[-transitionToActive <serviceId>]
[-transitionToStandby <serviceId>]
[-getServiceState <serviceId>]
[-checkHealth <serviceId>]
[-help <command>]

where <serviceId> is the rm-id.

  Note:

Even though -help lists the -failover option, it is not supported by yarn rmadmin.

Page generated September 3, 2015.