Manual Rolling Upgrade Procedure

This procedure assumes that the cluster being upgraded is 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:

1. Download the archive file from https://package.ezmeral.hpe.com/releases/.

   IMPORTANT

   To access the Data Fabric Internet repository, you must specify the email and token of an HPE Passport account. For more information, see Using the HPE Ezmeral Token-Authenticated Internet Repository.
2. Extract the archive file. When you upgrade each package, be sure to specify the full path to the files in this local directory:

   tar -xzvf <archive file>

3. Stop the CLDB if it is running on the node before putting that node into maintenance mode. Otherwise, the maintenance mode operation is not permitted:

   maprcli node services -name cldb -action stop -nodes <hostname>

4. Set the node to maintenance mode:

   sudo maprcli node maintenance -nodes <hostname> -timeoutminutes 30

5. Notify the CLDB that the node is going to be upgraded:

   sudo maprcli notifyupgrade start -node <hostname>

6. Stop Warden:

   sudo service mapr-warden stop

7. If ZooKeeper is installed on the node, stop ZooKeeper:

   service mapr-zookeeper stop

8. Check to ensure that all services are stopped:

   jps 
   46343 Jps
   3607 -- process information unavailable
   (Nothing running here)
   

9. Use the following command to view the Java alternatives menu, and set Java to JDK 11 or JDK 17:

   sudo update-alternatives --config java

10. Remove any patches installed on the node.

    • RHEL, Rocky, or SLES: sudo rpm -e mapr-patch
    • Ubuntu: sudo apt-get -y remove mapr-patch

11. Upgrade each data-fabric package on the node based on the defined package upgrade order by running this command for each package:

    • RHEL or SLES: yum upgrade <packagename>
    • Ubuntu: apt-get install --only-upgrade -o Dpkg::Options::="--force-overwrite" mapr-fileserver mapr-core mapr-cldb
      NOTE

      During the upgrade process on Ubuntu, the system displays dpkg warnings about overwriting. You can ignore these warnings.
12. Verify that the following packages are removed (these packages are obsolete in release 6.2 and later):
    • Remove mapr-mapreduce2 if it is present
    • Remove mapr-hadoop-core if you are upgrading a fileserver node that does not have the ResourceManager, NodeManager, or History Server. On such a node, only mapr-hadoop-util is needed after upgrading.
13. Ensure that every node has the following files in the /opt/mapr/conf directory:
    • maprserverticket
    • ssl_keystore
    • ssl_keystore.p12
    • ssl_keystore.pem
    • ssl_truststore
    • ssl_truststore.p12
    • ssl_truststore.pem
14. If ZooKeeper is installed on the node, start ZooKeeper:

    service mapr-zookeeper start

15. Start Warden:

    sudo service mapr-warden start

16. Check that the CLDB is running:

    maprcli node list

    If output is displayed, the CLDB is running. If not, start the CLDB.
17. Exit maintenance mode on the node and notify the CLDB about the upgraded version and the finished status of the upgrade process:

    sudo maprcli node maintenance -nodes <hostname> -timeoutminutes 0
    sudo maprcli config save -values {mapr.targetversion:"'cat /opt/mapr/MapRBuildVersion'"}
    sudo maprcli notifyupgrade finish -node <hostname>

18. Start ZooKeeper and Warden:

    service mapr-zookeeper start
    sudo service mapr-warden start

19. Wait for the containers to synchronize. Then run the following command and check that there is no output:

    /opt/mapr/server/mrconfig info containers resync local

    No output signifies that the containers are synchronized.