MapR 5.0 Documentation : Perform MapR Installer Pre-Upgrade Steps

When you use the MapR Installer to upgrade the MapR Core, the ecosystem component packages in the cluster are also upgraded. The MapR Installer does the following during an upgrade:

  • Automatically upgrades ecosystem components to the latest available MapR version of that component. For example, If you have Hive 0.13-1504 installed, the MapR Installer will update Hive 0.13 to the latest Hive 0.13 version that is available.  
  • Requires the upgrade of ecosystem components that are not compatible with the MapR cluster you are upgrading to. Refer to the Ecosystem Support Matrix to see which ecosystem components are supported with the version of MapR that you are upgrading to.
  • Allows you to upgrade existing ecosystem components if newer version are available. 

You may need to upgrade a supported version of an ecosystem component to a more recent supported version in order to ensure cross-compatibility among the ecosystem components in the cluster. Refer to the Ecosystem Support Matrix to check for compatibility between ecosystem components.

Complete the following pre-upgrade steps for each component that is installed in your cluster: 

Drill

If you have advanced configurations for Drill, complete the following steps to create a backup: 

  • To back up your storage plugins, complete the following steps:
    1. Start the Web Console. The Drill node that you use to access the Web Console must be a node that is currently running the Drillbit process.
    2. Click Storage.
    3. Click Update next to a storage plugin.
    4. Copy the configuration to a text file, and save the file.
    5. Repeat steps 3 and 4 for each storage plugin configuration that you want to save.
  • To back up drill-override.conf and drill-env.sh, navigate to /opt/mapr/drill/drill-<version>/conf, and copy the files to a location outside of the MapR installation directory.

    Example
    cp drill-override.conf drill-env.sh /home/max/drill_conf 

Flume 

Complete the following pre-upgrade step for Flume:

  • Back up Configuration Files
    If you have modified the configuration files in your current installation of Flume and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directory. Configuration files are located in /opt/mapr/flume/flume-<version>/conf/

HBase

Complete the following pre-upgrade steps for HBase:

  • Take Snapshot of the hbase Volume
    Take a snapshot of the hbase volume. The snapshot creates a backup of the volume data that you can use to recover your data in the event that corruption occurs during the upgrade process. 
     
  • Back up Configuration Files
    If you have modified the configuration files in your current installation of HBase and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration properties are located in /opt/mapr/hbase/hbase-<version>/conf/.  

Hive 

Complete the following steps for Hive:

  1. Back up the metastore database.

    mysqldump  -u<user> -p<passwd>  <metastore_db_name> -r metastore-db-dump.sql

     Perform this step to create a backup in case an error occurs during the Hive upgrade.
     

  2. Back up Configuration Files
    If you have modified the configuration files in your current installation of Hive and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directory. Configuration files are located in /opt/mapr/hive/hive-<version>/conf/

HttpFS

Complete the following pre-upgrade steps for HttpFS:

  • Back up Configuration Files
    If you have changed configuration properties, create a backup of the configuration files in a location outside of the MapR installation directory
    For example, you may want to back up the following configuration files:
    •  /opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/webapps/webhdfs/WEB-INF/web.xml
    • /opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/server.xml

    • /opt/mapr/httpfs/httpfs-1.0/share/hadoop/httpfs/tomcat/conf/tomcat-users.xml

Hue

Complete the following pre-upgrade steps for Hue:

  1. Stop the Hue service.

    maprcli node services -name hue -action stop -nodes <ip_address>
  2. Create a Hue database dump as a JSON object:

    For MySQL, PostgreSQL, or Oracle
    cd /opt/mapr/hue/hue-<version>/build/env/bin/
    source /opt/mapr/hue/hue-<version>/build/env/bin/activate
    ./hue dumpdata > dump-hue-<version>.json
    For SQLite
    cd /opt/mapr/hue/hue-<version>/desktop
    sqlite3 desktop.db .dump > ~/dump-hue-<version>-sqlite.bak

     

  3. Back up the Configuration Files
    If you have modified the configuration files in your current installation of Hue and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration properties are located in /opt/mapr/hue/hue-<version>/desktop/conf/.

Mahout

Complete the following pre-upgrade steps for Mahout:

  • Back up Configuration Files
    If you have modified the configuration files in your current installation of Mahout and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration files are located in /opt/mapr/mahout/mahout-<version>/conf/.

Oozie

Complete the following pre-upgrade steps for Oozie:

  1. Stop any jobs or coordinators that are in a RUNNING or SUSPENDED state. 

  2. Back up Configuration Files
    If you have modified the configuration files in your current installation of Oozie and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration properties are located in /opt/mapr/oozie/oozie-<version>/conf/.

Pig

Complete the following the following pre-upgrade step for Pig:

  • Back up Configuration Files
    If you have modified the configuration files in your current installation of Pig and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration properties are located in /opt/mapr/pig/pig-<version>/conf/

Sentry

Complete the following the following pre-upgrade step for Sentry:

  • Back up Configuration Files
    If you have modified the configuration files in your current installation of Sentry and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directory. Configuration files are located in /opt/mapr/sentry/sentry-<version>/conf/. 

Spark

Follow the pre-upgrade steps for the Spark mode that you use.

Spark Standalone

Complete the following the following pre-upgrade steps for Spark Standalone is installed:

  • Back up Configuration Files
    If you have modified the configuration files in your current installation of Spark and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration files are located in /opt/mapr/spark/spark-<version>/conf.  For example, if Spark SQL is configured to work with Hive, copy the /opt/mapr/spark/spark-<version>/conf/hive-site.xml file to a backup directory.
     
  • Shut down the spark-master and spark-historyserver services (if the spark-historyserver is running):

    maprcli node services -nodes <node-ip> -name spark-master -action stop
    maprcli node services -nodes <node-ip> -name spark-historyserver -action stop
  • As the mapr user, stop the slaves:

    /opt/mapr/spark/spark-<version>/sbin/stop-slaves.sh

Spark On YARN

Complete the following pre-upgrade steps for Spark on YARN:

  1. Back up Configuration files
    If you have modified the configuration files in your current installation of Spark and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directoryConfiguration files are located in /opt/mapr/spark/spark-<version>/conf.  For example, if Spark SQL is configured to work with Hive, copy the /opt/mapr/spark/spark-<version>/conf/hive-site.xml file to a backup directory.
     
  2. Shut down the spark-historyserver services (if the spark-historyserver is running):

    maprcli node services -nodes <node-ip> -name spark-historyserver -action stop

Sqoop1

 Complete the following pre-upgrade step for Sqoop1:

  • Back up Configuration Files
    If you have modified the configuration files in your current installation of Sqoop1 and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directory. Configuration files are located in /opt/mapr/sqoop/sqoop-<version>/conf/

Sqoop2

 Complete the following pre-upgrade steps for Sqoop2:

  • Back up the Sqoop2 repository
    For example, you can copy the repository to the /tmp directory:  

    cp -a /opt/mapr/sqoop/repository /tmp/
  • Back up Configuration Files
    If you have modified the configuration file in your current installation of Sqoop and you want to apply those changes to the updated version, create a backup of the configuration file in a location outside of the MapR installation directory. Configurations are located in the sqoop.properties file ( /opt/mapr/sqoop/sqoop-<version>/server/conf/sqoop.properties) .

Storm

 Complete the following pre-upgrade steps for Storm:

  • Stop the currently running topology
    This is required so that you can submit a new topology under the same name after the upgrade completed:

    storm kill <topology-name>
  • Back up configuration files
    If you have modified the configuration files in your current installation of Storm and you want to apply those changes to the updated version, create a backup of the configuration files in a location outside of the MapR installation directory.  Configuration files are located in /opt/mapr/storm/storm-<version>/conf/.