<?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: orphan queries in running state in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125285#M47405</link>
    <description>&lt;P&gt;The only one was to increase the&amp;nbsp;"spark.databricks.execution.timeout" because the query needed more than 2.5h unfortunately&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Jul 2025 10:28:05 GMT</pubDate>
    <dc:creator>meanwhilefurthe</dc:creator>
    <dc:date>2025-07-15T10:28:05Z</dc:date>
    <item>
      <title>orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125257#M47390</link>
      <description>&lt;P&gt;We have a job submitted through the &lt;SPAN class=""&gt;Spark Connect API&lt;/SPAN&gt;, and running on Serverless Compute.&lt;/P&gt;&lt;P&gt;The job got canceled twice and left a total of 14 queries orphan, they are in a weird state because the running time is not increasing, but they are there showing up as running.&lt;/P&gt;&lt;P&gt;There is no UI for serverless compute, the spark ui is not available either given that the compute is managed by databricks too, the api for cancelling the queries returns an empty response which apparently is supposed to, but the queries are still there in a running state.&lt;/P&gt;&lt;P&gt;Any way to cancel these queries? There is no cancel button in the UI either..&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:11:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125257#M47390</guid>
      <dc:creator>meanwhilefurthe</dc:creator>
      <dc:date>2025-07-15T09:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125265#M47393</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/175167"&gt;@meanwhilefurthe&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;can you run&amp;nbsp;CANCEL QUERY &lt;SPAN class=""&gt;'your_query_id'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;replace your query id there.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:37:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125265#M47393</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-15T09:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125266#M47394</link>
      <description>&lt;P&gt;You can configure a timeout for your Spark queries by setting the spark.databricks.queryWatchdog.timeoutInSeconds configuration property. This will automatically terminate any query that exceeds the specified execution time, preventing them from becoming long-running orphans.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:38:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125266#M47394</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-15T09:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125268#M47396</link>
      <description>&lt;P&gt;Hey &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/173840"&gt;@Khaja_Zaffer&lt;/a&gt;,&amp;nbsp;appreciate your reply, but the cancel query does not work, it is a serverless compute, so if a new session is created, it can't communicate with the old one anymore.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:52:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125268#M47396</guid>
      <dc:creator>meanwhilefurthe</dc:creator>
      <dc:date>2025-07-15T09:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125269#M47397</link>
      <description>&lt;P&gt;We do have timeouts, and there also default timeouts too otherwise, the issue is not that the query is running for longer than that timeout, but that is in this weird state where it shows as running but it is not getting updated metrics of running time or anything like that&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:54:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125269#M47397</guid>
      <dc:creator>meanwhilefurthe</dc:creator>
      <dc:date>2025-07-15T09:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125271#M47398</link>
      <description>&lt;P&gt;I think we need to check internals on this issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;better create a ticket with databricks.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;!--  StartFragment   --&gt;&lt;SPAN class=""&gt;Please raise the ticket using this lik&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;A href="https://help.databricks.com/s/contact-us?ReqType=training" target="_blank" rel="noopener"&gt;https://help.databricks.com/s/contact-us?ReqType=training&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&amp;nbsp;Please explain the issue clearly so that it will be easy for supoort team to help easily. &lt;/SPAN&gt;&lt;!--  EndFragment   --&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:56:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125271#M47398</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-15T09:56:55Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125272#M47399</link>
      <description>&lt;P&gt;I already did and the support redirected me here. the ticket I opened is:&amp;nbsp;&lt;SPAN&gt;00699724&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 09:59:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125272#M47399</guid>
      <dc:creator>meanwhilefurthe</dc:creator>
      <dc:date>2025-07-15T09:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125281#M47402</link>
      <description>&lt;P&gt;Just asking are you using Azure cloud?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 10:18:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125281#M47402</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-15T10:18:14Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125283#M47403</link>
      <description>&lt;P&gt;ALSO, did you make any recent code changes or network changes?&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 10:21:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125283#M47403</guid>
      <dc:creator>Khaja_Zaffer</dc:creator>
      <dc:date>2025-07-15T10:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125284#M47404</link>
      <description>&lt;P&gt;nope, AWS&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 10:26:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125284#M47404</guid>
      <dc:creator>meanwhilefurthe</dc:creator>
      <dc:date>2025-07-15T10:26:38Z</dc:date>
    </item>
    <item>
      <title>Re: orphan queries in running state</title>
      <link>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125285#M47405</link>
      <description>&lt;P&gt;The only one was to increase the&amp;nbsp;"spark.databricks.execution.timeout" because the query needed more than 2.5h unfortunately&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jul 2025 10:28:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/orphan-queries-in-running-state/m-p/125285#M47405</guid>
      <dc:creator>meanwhilefurthe</dc:creator>
      <dc:date>2025-07-15T10:28:05Z</dc:date>
    </item>
  </channel>
</rss>

