<?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 DatabricksConnect from Python/AKS environment calling Databricks Cluster: Spark Query Call Hangs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricksconnect-from-python-aks-environment-calling-databricks/m-p/159093#M54788</link>
    <description>&lt;P&gt;I have Python 3.12 Pod in AKS using DatabricksConnect 18.1.1 connecting to Databricks cluster 18.1.&lt;/P&gt;&lt;P&gt;All works great and normally I see no issues running series of Spark queries&amp;nbsp;&lt;/P&gt;&lt;P&gt;But once a while, even without any load on dedicated cluster we have, query that normally completes under 10 seconds - does not return and will continue to show waiting on client side in AKS - even after 30 mins.&lt;/P&gt;&lt;P&gt;This seems like client call is hanging - not recognizing any issues with gRPC/Network or something else in between. Cluster health seems to be ok&lt;/P&gt;&lt;P&gt;Its not easily reproducible. Currently I have no timeouts set.&lt;/P&gt;&lt;P&gt;There is suggestion to use "&lt;SPAN&gt;databricks_http_timeout_seconds" as it seems like there is no default timeout set - any network errors are not picked up and client call is simply waiting. If I use this timeout , I am hoping to get failure at least in reasonable time and I can retry.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;There were also suggestions to set gRPC keepalive that might fix these network specific issues: (Ref:&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/databricks-connect-serverless-grpc-issue/td-p/154016" target="_blank"&gt;https://community.databricks.com/t5/data-engineering/databricks-connect-serverless-grpc-issue/td-p/154016&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;Can anyone suggest if this issue is noticed and will timeout and mainly "&lt;SPAN&gt;databricks_http_timeout_seconds" will fix this issue. OR there other suggestions that might help?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jun 2026 23:30:03 GMT</pubDate>
    <dc:creator>JTBS</dc:creator>
    <dc:date>2026-06-15T23:30:03Z</dc:date>
    <item>
      <title>DatabricksConnect from Python/AKS environment calling Databricks Cluster: Spark Query Call Hangs</title>
      <link>https://community.databricks.com/t5/data-engineering/databricksconnect-from-python-aks-environment-calling-databricks/m-p/159093#M54788</link>
      <description>&lt;P&gt;I have Python 3.12 Pod in AKS using DatabricksConnect 18.1.1 connecting to Databricks cluster 18.1.&lt;/P&gt;&lt;P&gt;All works great and normally I see no issues running series of Spark queries&amp;nbsp;&lt;/P&gt;&lt;P&gt;But once a while, even without any load on dedicated cluster we have, query that normally completes under 10 seconds - does not return and will continue to show waiting on client side in AKS - even after 30 mins.&lt;/P&gt;&lt;P&gt;This seems like client call is hanging - not recognizing any issues with gRPC/Network or something else in between. Cluster health seems to be ok&lt;/P&gt;&lt;P&gt;Its not easily reproducible. Currently I have no timeouts set.&lt;/P&gt;&lt;P&gt;There is suggestion to use "&lt;SPAN&gt;databricks_http_timeout_seconds" as it seems like there is no default timeout set - any network errors are not picked up and client call is simply waiting. If I use this timeout , I am hoping to get failure at least in reasonable time and I can retry.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;There were also suggestions to set gRPC keepalive that might fix these network specific issues: (Ref:&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/databricks-connect-serverless-grpc-issue/td-p/154016" target="_blank"&gt;https://community.databricks.com/t5/data-engineering/databricks-connect-serverless-grpc-issue/td-p/154016&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;Can anyone suggest if this issue is noticed and will timeout and mainly "&lt;SPAN&gt;databricks_http_timeout_seconds" will fix this issue. OR there other suggestions that might help?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2026 23:30:03 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricksconnect-from-python-aks-environment-calling-databricks/m-p/159093#M54788</guid>
      <dc:creator>JTBS</dc:creator>
      <dc:date>2026-06-15T23:30:03Z</dc:date>
    </item>
  </channel>
</rss>

