<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic workflow cluster was create error in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5320#M1771</link>
    <description>&lt;P&gt;&lt;/P&gt;&lt;P&gt;I set the workflow to run at 12:00 every day in the workflow, but the workflow failed with the error message below, and I don't know why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Run result unavailable: run failed with error message&lt;/P&gt;&lt;P&gt; Unexpected failure while waiting for the cluster (0506-023332-glkykcrs) to be ready: Cluster 0506-023332-glkykcrs is in unexpected state Terminated: UNEXPECTED_LAUNCH_FAILURE(SERVICE_FAULT): databricks_error_message:com.google.common.util.concurrent.UncheckedExecutionException: com.databricks.rpc.ReliableJettyClient$MaxRetriesExceededException: Max retries exhausted with RPC com.databricks.api.proto.central.GetCustomerStorageInfo, max retry count: 3&lt;/P&gt;</description>
    <pubDate>Tue, 25 Apr 2023 04:10:37 GMT</pubDate>
    <dc:creator>owen1</dc:creator>
    <dc:date>2023-04-25T04:10:37Z</dc:date>
    <item>
      <title>workflow cluster was create error</title>
      <link>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5320#M1771</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;P&gt;I set the workflow to run at 12:00 every day in the workflow, but the workflow failed with the error message below, and I don't know why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Run result unavailable: run failed with error message&lt;/P&gt;&lt;P&gt; Unexpected failure while waiting for the cluster (0506-023332-glkykcrs) to be ready: Cluster 0506-023332-glkykcrs is in unexpected state Terminated: UNEXPECTED_LAUNCH_FAILURE(SERVICE_FAULT): databricks_error_message:com.google.common.util.concurrent.UncheckedExecutionException: com.databricks.rpc.ReliableJettyClient$MaxRetriesExceededException: Max retries exhausted with RPC com.databricks.api.proto.central.GetCustomerStorageInfo, max retry count: 3&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 04:10:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5320#M1771</guid>
      <dc:creator>owen1</dc:creator>
      <dc:date>2023-04-25T04:10:37Z</dc:date>
    </item>
    <item>
      <title>Re: workflow cluster was create error</title>
      <link>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5321#M1772</link>
      <description>&lt;P&gt;@Sangwoo Lee​&amp;nbsp;Hi, This seems to be an infra related issue. Please check the event logs to understand if the clusters were available to be provisioned from your Cloud provider. If this problem keep persisting, you can also try to choose an instance that is more commonly available in your Cloud region. We faced these kind of issues in All Purpose cluster spinning while requesting for high compute machines in AWS. &lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 07:02:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5321#M1772</guid>
      <dc:creator>pvignesh92</dc:creator>
      <dc:date>2023-04-25T07:02:01Z</dc:date>
    </item>
    <item>
      <title>Re: workflow cluster was create error</title>
      <link>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5322#M1773</link>
      <description>&lt;P&gt;Hello @Sangwoo Lee​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As mentioned by vignesh, it seems like an infra related issue. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Does the user (which executes the job) has access to start a cluster?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Incase if it is not an access issue and Incase if you are starting a lot of workflow jobs together at the same time, try scheduling one job 5 minutes earlier ( just to start the cluster) - and schedule the remaining jobs to start together after 5 minutes. Idea is to have the cluster available already when the majority of the jobs need it.   &lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 09:08:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/workflow-cluster-was-create-error/m-p/5322#M1773</guid>
      <dc:creator>Murthy1</dc:creator>
      <dc:date>2023-04-25T09:08:27Z</dc:date>
    </item>
  </channel>
</rss>

