<?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 Mysterious simultaneous long-running Databricks Workflows in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/mysterious-simultaneous-long-running-databricks-workflows/m-p/3061#M243</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This happened across 4x seemingly unrelated workflows at the same time of the day - all 4x workflows eventually completed successfully. It appeared that all workflows sat idling despite triggering via the Jobs API. The two symptoms I have observed are for 3x workflows, Databricks intiating its cluster creation only 3hrs(!) after the request was issued via Jobs API and the last workflow, where a cluster was promptly created but idling on a task/notebook for 3hrs despite none of its individual cells reporting any duration longer than a few seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a nutshell, the workflows weren't delayed in processing, reading, writing or doing any other work. They looked like they all suddenly sat idle for 3hrs at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Driver logs &amp;amp; Log4js don't reveal anything. We are on the Azure cloud using Spot instances so I was wondering if it could have anything to do with eviction, however nothing in the logs suggests this was happening. Could it be the Azure cloud slow in providing compute?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before I get dive deeper and get lost in the rabbit hole I wanted to poll the community first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tim.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jun 2023 17:12:37 GMT</pubDate>
    <dc:creator>timothy_uk</dc:creator>
    <dc:date>2023-06-14T17:12:37Z</dc:date>
    <item>
      <title>Mysterious simultaneous long-running Databricks Workflows</title>
      <link>https://community.databricks.com/t5/data-engineering/mysterious-simultaneous-long-running-databricks-workflows/m-p/3061#M243</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This happened across 4x seemingly unrelated workflows at the same time of the day - all 4x workflows eventually completed successfully. It appeared that all workflows sat idling despite triggering via the Jobs API. The two symptoms I have observed are for 3x workflows, Databricks intiating its cluster creation only 3hrs(!) after the request was issued via Jobs API and the last workflow, where a cluster was promptly created but idling on a task/notebook for 3hrs despite none of its individual cells reporting any duration longer than a few seconds.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a nutshell, the workflows weren't delayed in processing, reading, writing or doing any other work. They looked like they all suddenly sat idle for 3hrs at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Driver logs &amp;amp; Log4js don't reveal anything. We are on the Azure cloud using Spot instances so I was wondering if it could have anything to do with eviction, however nothing in the logs suggests this was happening. Could it be the Azure cloud slow in providing compute?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before I get dive deeper and get lost in the rabbit hole I wanted to poll the community first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tim.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 17:12:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/mysterious-simultaneous-long-running-databricks-workflows/m-p/3061#M243</guid>
      <dc:creator>timothy_uk</dc:creator>
      <dc:date>2023-06-14T17:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: Mysterious simultaneous long-running Databricks Workflows</title>
      <link>https://community.databricks.com/t5/data-engineering/mysterious-simultaneous-long-running-databricks-workflows/m-p/3062#M244</link>
      <description>&lt;P&gt;Hi @Timothy Lin​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Great to meet you, and thanks for your question! &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's see if your peers in the community have an answer to your question. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 17 Jun 2023 09:28:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/mysterious-simultaneous-long-running-databricks-workflows/m-p/3062#M244</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2023-06-17T09:28:49Z</dc:date>
    </item>
  </channel>
</rss>

