<?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 Re: Concurrent Workflow Jobs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/102618#M41180</link>
    <description>&lt;P&gt;It was an internal bug resolved with managing different parameters for each loop jobs.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Dec 2024 07:49:32 GMT</pubDate>
    <dc:creator>holychs</dc:creator>
    <dc:date>2024-12-19T07:49:32Z</dc:date>
    <item>
      <title>Concurrent Workflow Jobs</title>
      <link>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/101098#M40541</link>
      <description>&lt;P&gt;Hi Community,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to run a Databricks workflow job using run_job_task under a for_loop. I have set the concurrent jobs as 2.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can see 2 iteration jobs getting triggered successfully. But both fail with an error:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN&gt;"ConnectException: Connection refused (Connection refused)&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;EM&gt;Error while obtaining a new communication channel"&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;Contradictory to the fact that same job gets completed successfully with concurrency as 1.&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;Cluster Configuration:&amp;nbsp;&lt;EM&gt;Driver: Standard_DS5_v2 · Workers: Standard_DS5_v2 · 4-8 workers&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 05 Dec 2024 16:02:16 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/101098#M40541</guid>
      <dc:creator>holychs</dc:creator>
      <dc:date>2024-12-05T16:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: Concurrent Workflow Jobs</title>
      <link>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/101106#M40543</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/135150"&gt;@holychs&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did you encounter any error messages related to an OOM (Out of Memory) error?&lt;BR /&gt;It’s possible that the driver node of the cluster doesn’t have sufficient resources (CPU, memory) to handle multiple concurrent jobs.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2024 16:53:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/101106#M40543</guid>
      <dc:creator>Takuya-Omi</dc:creator>
      <dc:date>2024-12-05T16:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: Concurrent Workflow Jobs</title>
      <link>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/102618#M41180</link>
      <description>&lt;P&gt;It was an internal bug resolved with managing different parameters for each loop jobs.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 07:49:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/concurrent-workflow-jobs/m-p/102618#M41180</guid>
      <dc:creator>holychs</dc:creator>
      <dc:date>2024-12-19T07:49:32Z</dc:date>
    </item>
  </channel>
</rss>

