<?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 ISSUE: PySpark task exception handling on &amp;quot;Shared Compute&amp;quot; cluster in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/issue-pyspark-task-exception-handling-on-quot-shared-compute/m-p/86368#M37315</link>
    <description>&lt;P&gt;&lt;SPAN&gt;I am experiencing an issue with a PySpark job that behaves differently depending on the compute environment in Databricks. And this is blocking us from deploying the job into the PROD environment for our planned release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Specifically:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- When running the job on a personal cluster, everything works as expected. All exceptions within the try/catch blocks are successfully caught and handled.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- However, when I run the same job on a shared cluster, it fails, and no exceptions are being caught by the try/catch blocks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any guidance or insights you could provide would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Example (running piece of code in a workspace notebook):&amp;nbsp;&lt;A href="https://github.com/user-attachments/assets/78b38c5a-98f6-4bb0-82c3-45946d6c5500" target="_blank" rel="noopener"&gt;https://github.com/user-attachments/assets/78b38c5a-98f6-4bb0-82c3-45946d6c5500&lt;/A&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;Any ideas?&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/85537"&gt;@andrews&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Aug 2024 13:15:27 GMT</pubDate>
    <dc:creator>geronimo_signol</dc:creator>
    <dc:date>2024-08-29T13:15:27Z</dc:date>
    <item>
      <title>ISSUE: PySpark task exception handling on "Shared Compute" cluster</title>
      <link>https://community.databricks.com/t5/data-engineering/issue-pyspark-task-exception-handling-on-quot-shared-compute/m-p/86368#M37315</link>
      <description>&lt;P&gt;&lt;SPAN&gt;I am experiencing an issue with a PySpark job that behaves differently depending on the compute environment in Databricks. And this is blocking us from deploying the job into the PROD environment for our planned release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Specifically:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;- When running the job on a personal cluster, everything works as expected. All exceptions within the try/catch blocks are successfully caught and handled.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- However, when I run the same job on a shared cluster, it fails, and no exceptions are being caught by the try/catch blocks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any guidance or insights you could provide would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Example (running piece of code in a workspace notebook):&amp;nbsp;&lt;A href="https://github.com/user-attachments/assets/78b38c5a-98f6-4bb0-82c3-45946d6c5500" target="_blank" rel="noopener"&gt;https://github.com/user-attachments/assets/78b38c5a-98f6-4bb0-82c3-45946d6c5500&lt;/A&gt;&lt;/P&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;Any ideas?&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/85537"&gt;@andrews&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2024 13:15:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/issue-pyspark-task-exception-handling-on-quot-shared-compute/m-p/86368#M37315</guid>
      <dc:creator>geronimo_signol</dc:creator>
      <dc:date>2024-08-29T13:15:27Z</dc:date>
    </item>
  </channel>
</rss>

