Upgrading Sentry

Complete the following steps to upgrade manually. If you installed Sentry with the MapR Installer, use the latest version of the MapR Installer to perform the upgrade.

About this task

Procedure

Update repositories.
MapR's rpm and deb repositories always contain the Sentry version recommended for the MapR core release associated with that repository. You can connect to an internet repository or prepare a local repository with any version of Spark you need. You can also manually download packages. If you plan to install from a repository, complete the following steps each node where Sentry is installed:
1. Verify that the repository is configured correctly. See Preparing Packages and Repositories for information about setting up your ecosystem repository.
2. Update the repository cache.
  On RedHat/CentOS:
```
yum clean all
```
  On Ubuntu:
```
apt-get update
```
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/.
Use one of the following methods to upgrade Sentry:
- Use a package manager to install new packages from the repository.
  - On RedHat/CentOS:
```
yum upgrade mapr-sentry
```
  - On Ubuntu:
```
apt-get install mapr-sentry
```
  - On SUSE:
```
zypper update mapr-sentry
```
- Keep a prior version and install a newer version.
  To keep the prior version when installing a new version, you must manually install the package file for the new version.
  - On RedHat/CentOS or SUSE:
    1. Download the RPM package file from http://package.mapr.com/releases/ecosystem-all/.
    2. Install the package with rpm.
```
rpm -i --force mapr-sentry-<version>.rpm
```
  - On Ubuntu:
    This process is not supported on Ubuntu, because apt-get and dpkg cannot manage multiple versions of a package with the same name.
Sentry installs into separate directories named after the version, such as /opt/mapr/sentry/sentry-<version>/, so the files for multiple Sentry versions can co-exist.
Migrate Custom Configurations (optional).
Migrate any custom configuration settings into the new default files in the conf directory (/opt/mapr/sentry/sentry-<version>/conf/)