MapReduce (MRv1) JobTracker High Availability

Note: This page contains references to CDH 5 components or features that have been removed from CDH 6. These references are only applicable if you
are managing a CDH 5 cluster with Cloudera Manager 6. For more information, see Deprecated Items.

Follow the instructions in this section to configure high availability (HA) for JobTracker.

You can use Cloudera Manager to configure CDH 4.3 or higher for JobTracker high availability (HA). Although it is possible to configure JobTracker HA with CDH 4.2, it is not recommended.
Rolling restart, decommissioning of TaskTrackers, and rolling upgrade of MapReduce from CDH 4.2 to CDH 4.3 are not supported when JobTracker HA is enabled.

Cloudera Manager supports automatic failover of the JobTracker. It does not provide a mechanism to manually force a failover through the Cloudera Manager user interface.

Important: Enabling or disabling JobTracker HA will cause the previous monitoring history to become unavailable.

Enabling JobTracker High Availability

The Enable High Availability workflow leads you through adding a second (standby) JobTracker:

Go to the MapReduce service.

Select Actions > Enable High Availability. A screen showing the hosts that
are eligible to run a standby JobTracker displays. The host where the current JobTracker is running is not available as a choice.

Select the host where you want the Standby JobTracker to be installed, and click Continue.

Enter a directory location on the local filesystem for each JobTracker host. These directories will be used to store job configuration data.

You may enter more than one directory, though it is not required. The paths do not need to be the same on both JobTracker hosts.

If the directories you specify do not exist, they will be created with the appropriate permissions. If they already exist, they must be empty and have the appropriate permissions.

If the directories are not empty, Cloudera Manager will not delete the contents.

Optionally use the checkbox under Advanced Options to force initialize the ZooKeeper znode for auto-failover.

Click Continue. Cloudera Manager runs a set of commands that stop the MapReduce service, add a standby JobTracker and Failover controller, initialize the
JobTracker high availability state in ZooKeeper, create the job status directory, restart MapReduce, and redeploy the relevant client configurations.

Disabling JobTracker High Availability

Select which JobTracker (host) you want to remain as the single JobTracker, and click Continue. Cloudera Manager runs a set of commands that stop the
MapReduce service, remove the standby JobTracker and the Failover Controller, restart the MapReduce service, and redeploy client configurations.

If this documentation includes code, including but not limited to, code examples, Cloudera makes this available to you under the terms of the Apache License, Version 2.0, including any required
notices. A copy of the Apache License Version 2.0 can be found here.