This is the documentation for Cloudera Manager 4.8.4.
Documentation for other versions is available at Cloudera Documentation.

Managing Licenses

When you install Cloudera Manager, you can choose to install Cloudera Standard (no license required), Cloudera Enterprise (which requires a license) or a 60-day trial of Cloudera Enterprise.

Continue reading:

About Trial Licenses

You can use the trial license only once; once the 60-day trial period has expired or you have ended the trial, you cannot restart it.

When your 60-day trial ends, features will continue to work until you restart the Cloudera Manager server. However, you will not be able to log in again until you restart the server. However, data or configurations associated with the disabled functions will not be deleted, and will become available again if you install an Enterprise license. Trial expiration (or termination) will have the following effects:
  • Only local users will be able to log in (no LDAP authentication).
  • Configuration History will be unavailable.
  • SNMP alerts will not longer occur.
  • Operation Reports will be inaccessible (but will remain in the database).
  • Replication jobs (available with BDR) will no longer run.
  • Commands such as Rolling Restart, History and Rollback (under the Configuration tab), Send Diagnostic Data, Replication, and starting the Navigator role will not be available or will be disabled.

Accessing the License Page

To access the license page, select Administration > License.

If you have a license installed, the license page indicates its status (for example, whether your license is currently valid) and shows you the owner, the license key, and the expiration date of the license, if there is one. This does not appear if you are running Cloudera Standard. Note that currently no Add-Ons are shown, even if you have licenses for Add-ons such as BDR, Navigator, RTD, or RTQ.

At the right side of the page a table shows the usage of licensed products based on the number of nodes with those products installed. Each cell in the table shows the number of copies of the product installed per cluster, as well as the total copies installed on nodes under management by this Cloudera Manager server. You move the cursor over the to see an explanation of each item.

  • An Enterprise Core node is any host running one or more of the following: HDFS NameNode, HDFS DataNode, ZooKeeper Server, any non-Gateway Hive role.
  • An Enterprise BDR node is any billable host in a cluster used for backup.
  • An Enterprise RTD node is any host running one or more of the following: HBase RegionServer, HBase Master, ZooKeeper Server, HDFS NameNode.
  • An Enterprise RTQ node is any host running one or more of the following: Impala StateStore, Impala Daemon, HDFS NameNode.
  • A Navigator node is any billable host in a cluster managed by a CM instance running Navigator.

Ending a Cloudera Enterprise Trial

If you are using the trial edition the License page indicates when your license will expire. However, you can end the trial at any time (prior to expiration) as follows:
  1. On the License page, click End Trial.
  2. Confirm that you want to end the trial.
  3. Restart the Cloudera Manager server. Log in to your Cloudera Manager server host and restart the server from the command line. After the server has restarted, the Cloudera Manager login page appears.
  4. After you log back in, you may notice that the Reports Manager and Cloudera Navigator roles still appear. However, these roles are stopped, and cannot be restarted because they are unlicensed.
  5. Restart the Cloudera Management Services, HBase, HDFS, and Hive services to pick up configuration changes.

Upgrading From Cloudera Standard to a Cloudera Enterprise Trial

To start a 60-day Trial, on the License page, click Try Cloudera Enterprise for 60 Days.

  1. Cloudera Manager displays a pop-up describing the features enabled with Cloudera Enterprise. Click OK to proceed.
  2. Log in to the Cloudera Manager server host and restart the server from the command line. When the server has restarted, the Cloudera Manager Admin Console login page appears.
  3. Log in to the Admin Console.
  4. Configure the additional roles that are enabled.
    1. Designate a host for the Reports Manager role.
    2. Enter the credentials for the database to be used by the Reports Manager. Assuming you have not set up an external database, you can use the Embedded Database for this. Click Test Connection to verify connectivity to the Database, the click Continue.
    3. Review and accept any configuration changes (typically there are none). Click Accept.
  5. At this point, your installation is upgraded. Click Continue. The Home page displays.
  6. Start the Reports Manager role:
    1. In the Cloudera Management Services table, click the MGMT service.
    2. Click the Instances tab.
    3. Check the checkbox next to reportsmanager.
    4. Select Actions for Selected > Start and confirm Start in the pop-up.
    5. Click Close.
  7. Optionally add and start the Cloudera Navigator role. For information on Cloudera Navigator, see Cloudera Navigator documentation.
    1. Click the Add button.
    2. Select the host where you want the Navigator Server role to be hosted, and click Continue.
    3. Because Cloudera Navigator is separately licensed, you are presented with a license statement. Click Accept to enable the license for this feature.
    4. Enter the credentials for the database to be used by the Navigator Server. Assuming you have not set up an external database, you can use the Embedded Database for this. Click Test Connection to verify connectivity to the Database, the click Continue.
    5. Review and accept any configuration changes (typically there are none). Click Accept. This returns you to the Instances page.
    6. Check the checkbox next to navigator.
    7. Select Actions for Selected > Start and confirm Start in the pop-up.
    8. Click Close.
    9. If you have an Impala service, configure the Impala audit log directory:
      1. Go to the Impala service.
      2. Select Configuration > View and Edit.
      3. In the Search box, type Impala Daemon Audit Log Directory.
      4. Specify a value for the directory and click Save Changes.
      5. Select Actions > Restart, confirm Restart, and click Close to close the commands window when the command completes.
    10. Restart all audited services for auditing to go into effect.

Upgrading From a Cloudera Enterprise Trial to Cloudera Enterprise

  1. Purchase a Cloudera Enterprise license from Cloudera.
  2. On the License page, click Upload a Cloudera Enterprise License.
  3. Click the document icon to the left of the Select a License File text field.
  4. Navigate to the location of your license file, click the file, and click Open.
  5. Click Upload.

Upgrading From Cloudera Standard to Cloudera Enterprise

  1. Purchase a Cloudera Enterprise license from Cloudera.
  2. On the License page, click Upload a Cloudera Enterprise License.
  3. Click the document icon to the left of the Select a License File text field.
  4. Navigate to the location of your license file, click the file, and click Open.
  5. Click Upload.
  1. Cloudera Manager displays a pop-up describing the features enabled with Cloudera Enterprise. Click OK to proceed.
  2. Log in to the Cloudera Manager server host and restart the server from the command line. When the server has restarted, the Cloudera Manager Admin Console login page appears.
  3. Log in to the Admin Console.
  4. Configure the additional roles that are enabled.
    1. Designate a host for the Reports Manager role.
    2. Enter the credentials for the database to be used by the Reports Manager. Assuming you have not set up an external database, you can use the Embedded Database for this. Click Test Connection to verify connectivity to the Database, the click Continue.
    3. Review and accept any configuration changes (typically there are none). Click Accept.
  5. At this point, your installation is upgraded. Click Continue. The Home page displays.
  6. Start the Reports Manager role:
    1. In the Cloudera Management Services table, click the MGMT service.
    2. Click the Instances tab.
    3. Check the checkbox next to reportsmanager.
    4. Select Actions for Selected > Start and confirm Start in the pop-up.
    5. Click Close.
  7. Optionally add and start the Cloudera Navigator role. For information on Cloudera Navigator, see Cloudera Navigator documentation.
    1. Click the Add button.
    2. Select the host where you want the Navigator Server role to be hosted, and click Continue.
    3. Because Cloudera Navigator is separately licensed, you are presented with a license statement. Click Accept to enable the license for this feature.
    4. Enter the credentials for the database to be used by the Navigator Server. Assuming you have not set up an external database, you can use the Embedded Database for this. Click Test Connection to verify connectivity to the Database, the click Continue.
    5. Review and accept any configuration changes (typically there are none). Click Accept. This returns you to the Instances page.
    6. Check the checkbox next to navigator.
    7. Select Actions for Selected > Start and confirm Start in the pop-up.
    8. Click Close.
    9. If you have an Impala service, configure the Impala audit log directory:
      1. Go to the Impala service.
      2. In the Search box, type Impala Daemon Audit Log Directory.
      3. Specify a value for the directory and click Save Changes.
      4. Select Actions > Restart, confirm Restart, and click Close to close the commands window when the command completes.
    10. Restart all audited services for auditing to go into effect.