Adding Query Processor service to a cluster

The Query Processor service indexes Hive and Tez events and provides APIs to access them. It is required if you want to view the Queries tab (query history and query details) on the Hue Job Browser. You must install the Query Processor service on your CDP Private Cloud Base clusters manually.

You can either install the Query Processor service as a dependency while adding the Hue service or after adding the Hue service.

This task assumes that you already have a PostgreSQL database installed on a host in your cluster.

Next, you need to create a database for the Query Processor service with the required roles. To create the Query Processor database:
  1. SSH into your database host as a root user.
  2. Start the psql terminal by entering the following command:
    sudo -u postgres psql
  3. Run the following statement while specifying the username, password, and a database name for the Query Processor:
  1. Log in to Cloudera Manager as an Administrator.
  2. Go to Clusters > > Add Service.
  3. Select Query Processor on the Add Service to Cluster page and click Continue.
    The required dependencies are automatically selected.
  4. Select the host on which you want to install the Query Processor by clicking View By Host. Then click Continue.
  5. Select the database type, and specify the database hostname, database name, and username and password to access the database on the Setup Database page and click Test Connection.
    After the connection is verified, click Continue.
  6. On the Review Changes page, accept the default settings and click Continue.
    If Kerberos or Auto-TLS are set up on your Data Hub cluster, then the corresponding settings are automatically configured.
    The Command Details page is displayed, which shows the status of the installation and configuration.
  7. Click Continue if the operation is successful.
  8. Click Finish on the Summary page.
You are redirected to the Cloudera Manager home page. You can now see the Query Processor service listed within your cluster.