Cloudera Docs

Troubleshooting upgrade issues

The following section lists common issues related to upgrading Data Hubs.

Failed to start role of service profiler_scheduler in cluster

While upgrading from Cloudera Runtime version 7.2.17 to 7.2.18, and specifically during the Data Hub OS upgrade step, the cluster goes into the failure state. The following message is seen:
NODE_FAILURE:
New node(s) could not be added to the cluster. Reason Please find more details on Cloudera Manager UI. Failed command(s): Start(id=1546339088): Failed to start role profc6cf3856-PROFILER_SCHEDULER_AGENT-484032cb8f17cacf9e684efe50 of service profiler_scheduler in cluster cdp-dc-profilers-258395ef.

Impact on Data Catalog profilers:

If the Data Hub is not created, the profilers will not be created in Cloudera Runtime 7.2.18 version.

Workaround:

You must use the following process to bring up the Data Catalog profilers in the 7.2.18 version.

  1. First you must delete your existing 7.2.17 clusters. For more information, see Deleting profiler cluster.
  2. Next, after you upgrade to the 7.2.18 Data Lake, then you can launch the Data Catalog profilers. For more information, see Launch profiler cluster.