Setting Up Navigator Metadata Server

By default, the Cloudera Manager installation wizard assigns the Navigator Audit Server and Navigator Metadata Server roles to the same Cloudera Management Service host. This configuration can support small clusters but larger production clusters often need these roles distributed to different nodes for better performance. You can distribute these roles to different nodes at install time or you can move the Navigator Metadata Server later if necessary.

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

1. Configure the database where policies, roles, and audit report metadata is stored. For production environments, Cloudera supports only external databases. The internal PostgreSQL database should be used for non-production clusters only, such as proof-of-concept.
   • For external databases (production environments): The database should be up and running before you add the Navigator Metadata Server role to the cluster. You must have the database schema name (user name), password, and other details to provide when adding the role. When you have these ready, you can proceed.
   • For internal databases (non-production environments): No additional preliminary information is needed. You can proceed.
2. Log in to the Cloudera Manager Admin Console.
3. Select Clusters > Cloudera Management Service.
4. Click the Instances tab.
5. Click the Add Role Instances button. The Customize Role Assignments page displays and lists the nodes available to support additional roles, assuming the cluster has available resources. Reassign and customize role instances as needed.
6. Select the Navigator Metadata Server role and assign it to appropriate host for your cluster.
7. When finished, click Continue. The Database Setup page displays.
8. Click Use Custom Database.
9. In the Navigator Metadata Server section, enter the details of your database instance:
   • Database host name
   • Database type
   • Database name
   • Username
   • Password
   Here is an example of a configured custom (external) database instance that uses MySQL for the Navigator Metadata Server database:
   
   
   
   
10. Click Test Connection to verify the communication between the cluster and the external database. If the test fails, check the database settings and try again. If you selected embedded database, a message displays regarding database creation.
11. Click Continue.
12. The Cluster Setup Review Changes page displays.
13. Click Finish.

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

1. Log in to the Cloudera Manager Admin Console.
2. Select Clusters > Cloudera Management Service.
3. Click the Instances tab.
4. Click the link for the Navigator Metadata Server from the Role Type list. The Actions for Selected button activates and displays (1) for the selected role.
5. From the Actions for Selected (1) menu, select the Action you want to perform on this role instance:
   • Start
   • Stop
   • Restart
   • Enter Maintenance Mode
   • Exit Maintenance Mode
   • Delete
   A confirmation message displays giving you the option to Cancel or complete the specified Action.
6. Click Cancel to abandon the process, or click Action to execute the action.

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

1. Stop the Navigator Metadata Server. See Starting, Stopping, and Restarting a Navigator Metadata Server Role Instance for details.
2. Delete it from the existing host.
3. Add it to a new host. See Adding the Navigator Metadata Server Role for details.
4. If the storage directory is not on NFS/SAN, move the data to the same path on the new host. See Configuring the Navigator Metadata Server Storage Directory.
5. Start the Navigator Metadata Server.

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

(num_nav_elements * 200 bytes) + 2 GB

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

Navigator Metadata Server uses a Solr instance (a search engine) to index extracted metadata for fast search and retrieval. The searchable Solr documents are stored in a directory on the host on which the Navigator Metadata Server runs. The default location for the directory is /var/lib/cloudera-scm-navigator.

To change the location of the storage directory:

1. Log in to the Cloudera Manager Admin Console.
2. Select Clusters > Cloudera Management Service.
3. Click the Instances tab.
4. Click the link for the Navigator Metadata Server to select it.
5. From the Actions for Selected (1) menu, select Stop.
6. Open a terminal session and log in to the host configured to run Navigator Metadata Server.
7. Copy the contents of the current storage directory to the new location. When copying is complete, return to the Cloudera Manager Admin Console.
8. Click the Configuration tab.
9. Select Scope > Navigator Metadata Server.
10. Enter the directory path in the Navigator Metadata Server Storage Dir property. The property applies to the default role group, but you can apply to other role groups as needed. See Modifying Configuration Properties Using Cloudera Manager for details.
11. Click Save Changes. This change does not take effect until the Navigator Metadata Server role is restarted.
12. Click the Instances tab.
13. Click the link for the Navigator Metadata Server from the list of instances.
14. From the Actions for Selected menu, select Restart to restart the Navigator Metadata Server role instance.

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

The Cloudera Navigator console is accessed at port 7187 by default, on the host supporting the Navigator Metadata Server role. Follow the steps below to change setting.

1. Log in to the Cloudera Manager Admin Console.
2. Select Clusters > Cloudera Management Service.
3. Click the Configuration tab.
4. In the Search box, type the word "ports" to display properties.
5. Specify the port in the Navigator Metadata Server Port property. The property applies to the default role group, but you can apply to other role groups as needed. See Modifying Configuration Properties Using Cloudera Manager for details.
6. Click Save Changes.
7. Click the Instances tab.
8. Restart the Navigator Metadata Server role.

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

Cloudera Manager Required Role: Navigator Administrator (or Full Administrator)

Cloudera Navigator by default sends anonymous usage information to Cloudera for analysis. The usage information helps Cloudera improve Cloudera Navigator functionality and pro-actively identify areas of the product to enhance. The information is completely anonymous and cannot be traced to any customer installation.

To disable anonymous usage information collection:

1. Log in to the Cloudera Manager Admin Console.
2. Select Clusters > Cloudera Management Service.
3. Click the Configuration tab.
4. Under the Filter for Scope, click Navigator Metadata Server.
5. Click the Allow Usage Data Collection to clear the checkbox.
6. Click Save Changes.
7. Restart the Navigator Metadata Server role instance.

Cloudera Navigator stops emitting anonymous usage information.

This capability can be re-enabled at any time by clicking the Allow Usage Data Collection box that has been cleared.

If Navigator is running on a Kerberized cluster and the cluster is set up to use a custom keytab retrieval script, you need to manually put keytabs for HDFS and Hue principals into the Navigator home directory (typically /var/lib/cloudera-scm-navigator) for use by the Navigator web server.

If the keytabs are not available, you'll see Navigator Metadata Server log errors such as the following:

Error running extraction task.
  java.lang.RuntimeException: java.util.concurrent.ExecutionException:
  java.lang.RuntimeException: java.io.IOException: Login failure for hdfs/node.example.com@EXAMPLE.COM from keytab /var/lib/cloudera-scm-navigator/temp/1234/hadoop1234.keytab:
  javax.security.auth.login.LoginException: Unable to obtain password from user

Access to the Cloudera Manager Admin Console and the ability to change any of the settings in the table below requires the Cloudera Manager user role of Navigator Administrator or Full Administrator.