Associating a Workload Cluster with Telemetry Publisher

Steps for connecting your Workload cluster with the Telemetry Publisher service.

Describes how to associate a Workload Cluster with Telemetry Publisher by designating a host cluster with the Telemetry Publisher service role.
The following pre-tasks must be completed before associating a Workload cluster with Telemetry Publisher.
  • Verify that you have the JCE Policy installed before enabling the role in the Cloudera Manager Service.
  • Rename the Workload cluster with a human-readable name in Cloudera Manager.

    Workload XM identifies the cluster from a random string of 32 characters, such as 44a6e75e-8630-4773-9ea9-6272478e84c2, which is difficult to identify and manage. Cloudera recommends completing the following task to rename your Workload cluster.

    To rename a workload cluster:
    1. In a supported web browser on a Workload cluster, log in to Cloudera Manager.
    2. In Cloudera Manager, select Clusters, and then select the workload cluster that requires a human-readable name.
    3. From the Actions menu, select Rename Cluster.
    4. In the Name field of the Rename Cluster dialog box, enter a new name that is easily identifiable by you.
    5. Click Rename Cluster.
  1. In a supported web browser on a Workload cluster, log in to Cloudera Manager.
  2. In Cloudera Manager, select Clusters and then locate and select Cloudera Management Service.
  3. From the Actions menu, select Add Role Instances.
    The Add Role Instances to Cloudera Management Service opens.
  4. Do one of the following:
    • If a Telemetry Publisher role already exists, do nothing. Cloudera Manager does not let you add another.
    • If a Telemetry Publisher role does not exist, continue.
  5. Select a host for the Telemetry Publisher by doing one of the following:
    • If you are using Java 8, click Select a host and in the Hosts Selected page, select the check box by the side of the required host and click OK.
    • If you are using Java 7, configure Telemetry Publisher as follows:
      1. Go back to Cloudera Management Service and click the Configuration tab.
      2. Under Scope, select Telemetry Publisher.
      3. In the Search field, enter java configuration, which displays the Java Configuration Options for Telemetry Publisher filter.
      4. In Telemetry Publisher Default Group field, add the following property:
        -Dhttps.protocols=TLSv1.2 -Dhttps.cipherSuites=TLS_RSA_WITH_AES_256_CBC_SHA256
      5. Click Save Changes.
  6. Back in the Cloudera Manager Home page, select Clusters, Hive, and then Instances.
  7. Select the Role Type check box, which selects all the Hive Roles.
  8. From the Actions for Selected list, select Restart.
  9. In the Restart message, confirm restarting the HIVE roles by clicking Restart.
  10. Monitor the restart progress until the Successfully restarted service message appears and then click Close