This is documentation for MapR Version 5.0. You can also refer to MapR documentation for the latest release.

Skip to end of metadata
Go to start of metadata

Step 1. Planning the Upgrade | Step 2. Preparing to Upgrade | Step 3. Upgrading With the MapR Installer or Without the MapR Installer | Step 4. Upgrading MapR Clients 


When you upgrade the cluster, consider if your MapR client or your MapR POSIX client needs to be upgraded as well. See Planning Upgrades to MapR Clients.

To get a newer version of the Windows or Mac OS X MapR client, you must install the newer MapR client and reconfigure it. However, you can perform a package upgrade to get a newer version of the Linux MapR client. To get a newer version of the MapR POSIX client, you can perform a package upgrade.

Perform one or more of the following procedures to upgrade your MapR clients:

Upgrade the MapR Client on a Redhat, SUSE, or Ubuntu Server

To upgrade the MapR client on a Linux server, you must upgrade the mapr-client package.

  1. Configure the repository to point to the target release and operating system.
  2. Run the following command to upgrade the client package:
    • On  RedHat / CentOS:
      yum upgrade mapr-client
    • On SUSE:
      zypper update mapr-client
    • On Ubuntu:
      apt-get install mapr-client
Icon
When you upgrade the MapR client packages on a Linux server, the configuration files in  /opt/mapr/hadoop/hadoop-2.x.x directory are automatically copied into the active directory associated with the new hadoop 2.x.x directory. 

Upgrade the MapR Client on Windows

When you upgrade the MapR client on Windows, you need to rename the existing client directory, install the new version, and then merge the configuration files.

  1. Rename the existing client installation directory. 
    For example, you can rename \opt\mapr to \opt_old\mapr.
  2. Complete the installation steps in Install and Use the MapR Client.
  3. To retain existing configurations and accepts new defaults, merge the contents of the following directories in the previous installation with the ones in the new installation:
    • %MAPR_HOME%\hadoop\hadoop-2.x.x\etc\hadoop 
    • %MAPR_HOME%\hadoop\hadoop-0.20.0\conf 

Upgrade the MapR Client in Mac OS X

When you upgrade the MapR client on Mac OS X, you need to rename the existing client directory, install the new version, and then merge the configuration files.

  1. Rename the existing client installation directory. 
    For example, you can rename /opt/mapr to /opt_old/mapr.
  2. Complete the installation steps in Install and Use the MapR Client.
  3. To retain existing configurations and accepts new defaults, merge the contents of the following directories in the previous installation with the ones in the new installation:
    • opt/mapr/hadoop/hadoop-2.x.x/etc/hadoop 
    • opt/mapr/hadoop/hadoop-0.20.0/conf 

Upgrade the MapR POSIX Client on a Redhat, SUSE, or Ubuntu Server

To upgrade the MapR POSIX client on a Linux server, you must upgrade the mapr-loopbacknfs package.

  1. Stop the mapr-lookbacknfs service.

  2. Upgrade the mapr-loopbacknfs package.

    • On RedHat / CentOS:
      yum upgrade mapr-loopbacknfs

    • On SUSE:
      zypper update mapr-loopbacknfs

    • On Ubuntu:
      apt-get install mapr-loopbacknfs

  3.  Start the loopbacknfs service.

  4. Check the status of the loopbacknfs service.

Troubleshooting MapR POSIX Client Upgrades

If the mapr-loopbacknfs service fails to start after an upgrade, try the following troubleshooting step.

Check if a shared memory segment lock was the cause of the failure
  1. Open the loopbacknfs.log file. The loopbacknfs.log file is in the following directory: /usr/local/mapr-loopbacknfs/logs/
  2. Check for the following string: Create/Attach to shm failed
  3. If the string exists perform the following steps:
    1. Run the following command to identify the shmid of the lock: 
       ipcs -m | grep 0x0000161c
    2. Run the following command to remove the lock:
       ipcrm -m <shmid> 
    3. Start the mapr-loopbacknfs service.
  • No labels