Manual Rolling Upgrade Procedure

Complete the following upgrade steps for each node in each upgrade group.

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

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. Run commands to determine if a patch is installed. If the commands display no output, no patch is installed.

   • RHEL/CentOS and SLES: rpm -qa mapr-patch
   • Ubuntu: dpkg -l | grep mapr-patch

4. Get the default MapReduce mode for the cluster.

   maprcli cluster mapreduce get

5. Stop CLDB if it is running on the node, before putting that node in maintenance mode. Else, the maintenance mode operation is not permitted

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

6. Set the node to maintenance mode.

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

7. Notify the CLDB that the node is going to be upgraded.

   sudo maprcli notifyupgrade start -node <hostname>

8. Stop Warden.

   sudo service mapr-warden stop

9. If ZooKeeper is installed on the node, stop ZooKeeper.

   service mapr-zookeeper stop

10. Remove any patches installed on the node.

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

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

    • RHEL/CentOS or SLES: sudo rpm --quiet --force --nosignature -U </FullPathToPackage/PackageName.rpm>
    • Ubuntu: sudo dpkg --force-all -i </FullPathToPackage/PackageName.deb>
      NOTE During the upgrade process on Ubuntu, the system displays dpkg warnings about overwriting. You can ignore these warnings.

12. Configure the node.

    sudo /opt/mapr/server/configure.sh -R

13. If ZooKeeper is installed on the node, start ZooKeeper.

    service mapr-zookeeper start

14. Start Warden.

    sudo service mapr-warden start

15. Check that the CLDB is running. If output is displayed, the CLDB is running. If not, start CLDB.

    maprcli node list

16. Unset maintenance mode on the node, notify the CLDB about the upgraded version, and about 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>

17. Wait for the containers to synchronize, 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.