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 7.9.0 are supported only for clusters running release 6.1.x, 6.2.0, 7.0.0, 7.1.0, 7.2.0, 7.3.0, 7.4.0, 7.5.0, 7.6.x, 7.7.0, or 7.8.0.

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, run the following command: 

    maprcli node list -columns hostname,csvc
  • If the cluster is secure, the cluster admin user must have a security ticket created before running the upgrade. Otherwise, some upgrade commands will not run. The upgrade procedure assumes that the cluster to be upgraded is secure. Non-secure clusters must be secured before they can be upgraded. See Securing the Cluster Before Upgrading.

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 remains 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.
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 SLES, upgrade the mapr-core package first. Subsequent packages can be done in any order.
  • On SLES, 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 SLES)
  • mapr-core-internal
  • mapr-core
  • mapr-fileserver
  • mapr-gateway
  • mapr-hadoop-core*
  • mapr-historyserver*
  • mapr-keycloak (for upgrading from release 7.5.0 and later)
  • mapr-nfs
  • mapr-nodemanager*
  • mapr-resourcemanager*
  • mapr-s3server
  • mapr-webserver
  • mapr-zk-internal
  • mapr-zookeeper
*In release 6.2.0 and later, these packages are part of the EEP and must be reinstalled. See Installing Hadoop and YARN.

What's Next

See Manual Rolling Upgrade Procedure