Troubleshooting errors that occur after successful Cloudera Data Flow enablement

Concerning health due to “Workload Failed to Heartbeat”

If Cloudera Data Flow health is concerning for one of your environments, hover over the status icon and check the Alerts tab in the environment details to see details about the issue. Workload Failed to Heartbeat means that the Cloudera Control Plane has not received a recent heartbeat from the Cloudera Data Flow workload application running in your cloud account.

Cloudera Data Flow fails to receive heartbeats from a particular environment

Heartbeat failures can have several reasons. Make sure that:

• The associated Cloudera on cloud environment has been started and is running.
• There was no networking related change in your VPC/subnet configuration and that your networking setup still meets the requirements outlined in the Cloudera Data Flow Networking.

If the issue persists, open a support case with Cloudera.

Concerning Health due to Nearing Maximum Kubernetes Limit

When your Kubernetes cluster is close to its maximum node count, Cloudera Data Flow will show Concerning Health for the particular environment and display an Active Alert with more details about the boundaries. To return Cloudera Data Flow to Good Health you can adjust the maximum node number through the Edit Configuration option in the Environment actions menu.

Bad Health due to issues with the associated Cloudera on cloud environment

Certain issues with the associated Cloudera on cloud environment will result in Cloudera Data Flow reporting Bad Health for an environment. Once Cloudera Data Flow is in Bad Health you can no longer create or termnate flow deployments in the environment.

Bad Health due to Cloudera on cloud environment state

If the associated Cloudera on cloud environment is either unhealthy or in a starting/stopping state, Cloudera Data Flow will report Bad Health. To return Cloudera Data Flow to Good Health make sure that:

• The associated Cloudera on cloud environment has been started and is running.
• FreeIPA and DataLake are both running.

Bad Health due to Cloudera on cloud environment having been deleted

If the associated Cloudera on cloud environment has been deleted without disabling Cloudera Data Flow first, Cloudera Data Flow will report Bad Health indicating that it has been orphaned and required Cloudera on cloud services such as FreeIPA are no longer available in the environment.

You are not able to create new Flow Deployments for Cloudera Data Flow. You cannot recover Cloudera Data Flow health in this situation. Terminate your Flow Deployments and use the Disable Environment action to terminate Cloudera Data Flow and associated cloud infrastructure and enable Cloudera Data Flow again for a different Cloudera on cloud environment.