https://community.databricks.com/t5/data-engineering/cluster-start-issues/m-p/25633#M17868 <P>@Kunal Gaurav​&nbsp;, This status code only occurs in one of&nbsp;two conditions:</P><OL><LI>We’re able to request the instances for the cluster but can’t bootstrap them in time</LI><LI> We setup the containers on each instance, but can’t start the containers in time</LI></OL><P></P><P>this is an edge case in our service cleanup logic that some containers/clusters might be mis-identified as zombie resources, but there is actually no problem at all, we are working on optimizing the classifying logic and should have a fix deployed soon.</P><P></P><P>That being said <B>don't hesitate to create an Engineering Support ticket with the workspace id, cluser id and region</B> so databricks can confirm if something similar has happened in the region.</P> Fri, 18 Jun 2021 23:58:39 GMT Mooune_DBU 2021-06-18T23:58:39Z https://community.databricks.com/t5/data-engineering/cluster-start-issues/m-p/25632#M17867 <P>Some of the Jobs are failing in prod with below error message:</P><P>Can you please check and let us know the reason for this? These are running under pool cluster.</P><P></P><P>Run result unavailable: job failed with error message</P><P>Unexpected failure while waiting for the cluster (0604-056775-teaks96) to be ready.Cause Unexpected state for cluster (0604-056775-teaks96): UNEXPECTED_LAUNCH_FAILURE(SERVICE_FAULT): databricks_error_message:Encountered unexpected failure on instance InstanceId(63901da48df74d539b078907d929527d), failure code: DEFUNCT_RESOURCE</P><P>message: "Defunct Resource Detected"</P><P></P> Tue, 08 Jun 2021 11:54:32 GMT https://community.databricks.com/t5/data-engineering/cluster-start-issues/m-p/25632#M17867 User16826994223 2021-06-08T11:54:32Z https://community.databricks.com/t5/data-engineering/cluster-start-issues/m-p/25633#M17868 <P>@Kunal Gaurav​&nbsp;, This status code only occurs in one of&nbsp;two conditions:</P><OL><LI>We’re able to request the instances for the cluster but can’t bootstrap them in time</LI><LI> We setup the containers on each instance, but can’t start the containers in time</LI></OL><P></P><P>this is an edge case in our service cleanup logic that some containers/clusters might be mis-identified as zombie resources, but there is actually no problem at all, we are working on optimizing the classifying logic and should have a fix deployed soon.</P><P></P><P>That being said <B>don't hesitate to create an Engineering Support ticket with the workspace id, cluser id and region</B> so databricks can confirm if something similar has happened in the region.</P> Fri, 18 Jun 2021 23:58:39 GMT https://community.databricks.com/t5/data-engineering/cluster-start-issues/m-p/25633#M17868 Mooune_DBU 2021-06-18T23:58:39Z