Step 2: Manually Update Configuration Files

After upgrading MapR Core without the MapR Installer (using a manual offline, scripted, or rolling upgrade method ), update your configuration files.

Note: This task is applicable to all manual upgrade methods: offline, scripted, and rolling upgrades.
Important: After upgrading MapR and before enabling new features, all nodes in your cluster must be upgraded, all configuration files must be updated, and, if you are upgrading from 5.0 or earlier, the Base License file must be manually updated. See Step 3: Manually Update your License.

To manually update the configuration files:

  1. On all nodes, manually merge new configuration settings from the /opt/mapr/conf.new/warden.conf file into the /opt/mapr/conf/warden.conf file.
  2. On all nodes, manually merge new configuration settings from the files in the /opt/mapr/conf/conf.d.new/ directory to the files in the /opt/mapr/conf/conf.d/ directory.
Note: When hadoop common is updated along with MapR Core, a new directory is created for the new hadoop common version and the configuration files in the existing /opt/mapr/hadoop/hadoop-2.x.x directory are automatically copied into the active directory associated with the new hadoop 2.x.x directory. For example, when you upgrade from 4.1 to 5.x, configuration files that were in the hadoop-2.5.1 directory are copied into the hadoop-2.7.1 directory.
Important: If you are upgrading from 4.0.1, update scripts that point to files within the /opt/mapr/hadoop-2.4.1 directory to point to the new hadoop 2.x directory.