Manual Rolling Upgrade Description

In a manual rolling upgrade, you upgrade the data-fabric software one node at a time so that the cluster as a whole remains operational throughout the process.

Note: Rolling upgrades to release 6.2.0 are supported only for clusters running release 6.1.0 that have the latest mapr-core patch and the latest MEP (MEP 6.3.1).

Before you Upgrade

Before you begin a manual rolling upgrade, perform the following steps:

  • Determine the upgrade groups. To see a list of services on each node, you can run the following command:

    maprcli node list -columns hostname,csvc
  • If the cluster is secure, the data-fabric Admin user must have a security ticket created before running the upgrade. Otherwise, some upgrade commands will not run.

Group Upgrade Order

Upgrade cluster nodes in groups based on the services running on each node. Upgrade groups of nodes in the following order:

Group Nodes in this Group
1 Each node only has ZooKeeper. This establishes a stable ZooKeeper quorum on the new version, which will remain active through the rest of the upgrade process.
2 Each node only has a data-fabric gateway (mapr-gateway-x.x.x), or it has ZooKeeper. When upgrading from release 6.0 or 6.0.1 to release 6.1 or later, the data-fabric gateway must be upgraded before Fileserver.
3

Each node only has Fileserver or it has Fileserver, data-fabric gateway, and ZooKeeper.

4 Each node only has NodeManager or it has NodeManager, FileServer, data-fabric gateway, and ZooKeeper.
5 Each node only has ResourceManager or it has ResourceManager, NodeManager, FileServer, data-fabric gateway, and ZooKeeper. When you upgrade nodes in this group, upgrade nodes with the standby ResourceManagers before you upgrade the node with the active ResourceManager.
6

Each node has ResourceManager, NodeManager, FileServer, data-fabric gateway, and ZooKeeper.

7

Each node only has CLDB server or it has CLDB server, ResourceManager, NodeManager, FileServer, data-fabric gateway, and ZooKeeper. When you upgrade nodes in this group, upgrade nodes with the secondary CLDB before you upgrade the node with the primary CLDB.

Package Upgrade Order

When you upgrade each node, upgrade existing packages in the following order:

  • On all operating systems except SUSE, upgrade the mapr-core package first. Subsequent packages can be done in any order.
  • On SUSE, upgrade the mapr-compat-suse package first and the mapr-core package second. Subsequent packages can be done in any order.

The following is a list of the primary packages:

  • mapr-cldb
  • mapr-compat-suse (if upgrading on SUSE)
  • mapr-core-internal
  • mapr-core
  • mapr-fileserver
  • mapr-gateway
  • mapr-hadoop-core*
  • mapr-historyserver*
  • mapr-nfs
  • mapr-nodemanager*
  • mapr-resourcemanager*
  • mapr-webserver
  • mapr-zk-internal
  • mapr-zookeeper
*In release 6.2.0, these packages are part of MEP 7.0.0 and must be reinstalled. See Installing Hadoop and YARN.

What's Next

See Manual Rolling Upgrade Procedure