topic Job failed due to cluster being unusable since the driver is unhealthy in Warehousing & Analytics https://community.databricks.com/t5/warehousing-analytics/job-failed-due-to-cluster-being-unusable-since-the-driver-is/m-p/22523#M543 <P>I am currently unable to spin up any clusters in our databricks AWS environment.</P><P></P><P>When I attempt to start up an on-demand cluster, it remains in "pending" for 20+ minutes (on relatively small clusters which usually take 2-3 min to start up).</P><P></P><P>Similarly, all of my scheduled jobs are failing due to their job clusters not being able to start either. This is a sample error message:</P><P></P><P>"Run result unavailable: job failed with error message Unexpected failure while waiting for the cluster [cluster_name] to be ready. Cause Cluster [cluster_name] is unusable since the driver is unhealthy."</P><P></P><P>When I try to investigate the issue, the driver logs are completely empty. I have tried to initiate clusters with runtimes 9.1 and 10.4 and see the same issue.</P><P></P><P>Is this a databricks issue or an AWS issue?</P><P></P> Wed, 20 Apr 2022 14:59:18 GMT 602171 2022-04-20T14:59:18Z Job failed due to cluster being unusable since the driver is unhealthy https://community.databricks.com/t5/warehousing-analytics/job-failed-due-to-cluster-being-unusable-since-the-driver-is/m-p/22523#M543 <P>I am currently unable to spin up any clusters in our databricks AWS environment.</P><P></P><P>When I attempt to start up an on-demand cluster, it remains in "pending" for 20+ minutes (on relatively small clusters which usually take 2-3 min to start up).</P><P></P><P>Similarly, all of my scheduled jobs are failing due to their job clusters not being able to start either. This is a sample error message:</P><P></P><P>"Run result unavailable: job failed with error message Unexpected failure while waiting for the cluster [cluster_name] to be ready. Cause Cluster [cluster_name] is unusable since the driver is unhealthy."</P><P></P><P>When I try to investigate the issue, the driver logs are completely empty. I have tried to initiate clusters with runtimes 9.1 and 10.4 and see the same issue.</P><P></P><P>Is this a databricks issue or an AWS issue?</P><P></P> Wed, 20 Apr 2022 14:59:18 GMT https://community.databricks.com/t5/warehousing-analytics/job-failed-due-to-cluster-being-unusable-since-the-driver-is/m-p/22523#M543 602171 2022-04-20T14:59:18Z