Cloudera Enterprise 5.15.x | Other versions

Upgrading the Cloudera Navigator Data Management Component

Cloudera Manager Required Role: Full Administrator

The Cloudera Navigator Data Management component is upgraded automatically during the Cloudera Manager upgrade process. The component is not supported on Cloudera Express. It requires a Cloudera Enterprise license. See Managing Licenses for details about upgrading from trial licenses or Cloudera Express to Cloudera Enterprise.

Continue reading:

Before Upgrading the Cluster
Avoiding Out-of-Memory Errors During an Upgrade
Upgrading Cloudera Navigator
Backing Up Cloudera Navigator Data
Backing up Databases

Before Upgrading the Cluster

Review the Cloudera Navigator product compatibility matrix and confirm the compatibility of the Cloudera Navigator version and the Cloudera Manager version for the upgrade.
Review the Cloudera Navigator release notes, especially upgrade issues and limitations before upgrading.
Use the Purge capability provided in Cloudera Navigator 2.9 (and higher) to avoid out-of-memory errors during the upgrade process. See Avoiding Out-of-Memory Errors During an Upgrade for details.

Avoiding Out-of-Memory Errors During an Upgrade

A very large Navigator Metadata Server storage directory size can cause out-of-memory (OOM) errors, or can cause the upgrade to take an extremely long time (10 hours or more). To reduce the chances of OOM errors and the time it takes to upgrade:

Run the purge command before upgrading, and/or
Temporarily increase available JVM memory to 31 GB (but not more). Increasing JVM memory decreases available OS RAM, which is also needed for the upgrade, so give the JVM 31 GB max for the upgrade.

See Navigator Metadata Server Tuning for more information.

Upgrading Cloudera Navigator

The upgrade process can take three to four hours, depending on the amount of data in the Navigator Metadata Server storage directory.

Before upgrading Cloudera Navigator, you must:
- Stop the Navigator Metadata Server role.
- Back up the Navigator Metadata Server storage directory.
- Ensure the Navigator Metadata Server has sufficient memory to complete the upgrade.
- For systems using an Oracle database, grant additional privileges to the nav (or appropriate user name for the Navigator Audit Server). Log in to the database using SQL*Plus and run the following:
```
GRANT EXECUTE ON sys.dbms_crypto TO nav;
GRANT CREATE VIEW TO nav;
```
Upgrade Cloudera Manager, following the steps in Upgrading Cloudera Manager and CDH.
To upgrade from Cloudera Navigator 2.6 (and lower), log in to the Cloudera Navigator console. The Upgrading Navigator page displays. Depending on the amount of data in the Navigator Metadata Server storage directory, the upgrade process can take 3–4 hours or longer.
When the upgrade is complete, click Continue. The Cloudera Navigator console displays.

Backing Up Cloudera Navigator Data

Backups of Cloudera Manager include the data stored for Navigator Audit Server and Navigator Metadata Server data. See Backing up Cloudera Manager. Follow these steps if you need to back up either storage independently from Cloudera Manager:

Backup Navigator Audit Server Data

Navigator Audit Server stores audit information in a database instance. The audit metadata does not need to be backed up at the same time as the Navigator Metadata Server metadata.

Confirm the Navigator Audit Server database location and connection information.
To locate this information, log in to the Cloudera Manager Admin Console and go to Clusters > Cloudera Management Service. Click the Configuration tab. Select Scope > Navigator Audit Server and Category > Database. The results indicate the type, host, database name, and login account.
Using the appropriate tool for the database instance (such as MySQL), backup the database. See Backing Up Cloudera Navigator Data.

Backup Navigator Metadata Server Data

Navigator Metadata Server stores metadata in an embedded Solr data directory and in a database instance. Back up these locations together so the backups describe the same metadata state.

Shut down the Navigator Metadata Server role.
Backup the data directory.
The Navigator Metadata Server default directory is /var/lib/cloudera-scm-navigator. To confirm that this is the path your deployment uses, log in to the Cloudera Manager Admin Console and search for the Navigator Metadata Server Storage Dir property (nav.data.dir).
Backup the database instance.
- Confirm the Navigator Metadata Server database location and connection information.
  To locate this information, log in to the Cloudera Manager Admin Console and go to Clusters > Cloudera Management Service. Click the Configuration tab. Select Scope > Navigator Metadata Server. Select Category > Database. The results indicate the type, host, database name, and login account.
- Using the appropriate tool for the database instance (such as MySQL), backup the database. See Backing Up Cloudera Navigator Data.
Start the Navigator Metadata Server role.

Backing up Databases

Several steps in the backup procedures require you to back up various databases used in a CDH cluster. The steps for backing up and restoring databases differ depending on the database vendor and version you select for your cluster and are beyond the scope of this document.

See the following vendor resources for more information:

MariaDB 5.5: http://mariadb.com/kb/en/mariadb/backup-and-restore-overview/
MySQL 5.5: http://dev.mysql.com/doc/refman/5.5/en/backup-and-recovery.html
MySQL 5.6: http://dev.mysql.com/doc/refman/5.6/en/backup-and-recovery.html
PostgreSQL 8.4: https://www.postgresql.org/docs/8.4/static/backup.html
PostgreSQL 9.2: https://www.postgresql.org/docs/9.2/static/backup.html
PostgreSQL 9.3: https://www.postgresql.org/docs/9.3/static/backup.html
Oracle 11gR2: http://docs.oracle.com/cd/E11882_01/backup.112/e10642/toc.htm

Page generated May 18, 2018.