<?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: Queries Hanging Indefinitely in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144120#M4737</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I believe this is happening as you haven't got the right ports open to connect between your classic compute and the UC Metatstore. When you try to select 1 it works as it doesn't need to talk to the metastore but when you do show catalogs it is trying to reach the metastore and time out. You can verify this by running the following code.&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;import subprocess
workspace_url=spark.conf.get("spark.databricks.workspaceUrl")
ports = [443, 3306, 8443, 8444,]
for port in ports:
    check_cmd = f"nc -w2 -vz $(dig +short {workspace_url} | tail -n1) {port}"
    result = subprocess.run(check_cmd, shell=True, capture_output=True, text=True)
    print(f"Port {port}:", "Success" if result.returncode == 0 else "Failure")&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp; Note in the future you will also need ports 8445-8451 open as well as the ones in the code above. If any of these fail when you run the above script then you will need to open access to these ports. More details here&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/security/network/classic/customer-managed-vpc" target="_blank"&gt;https://docs.databricks.com/aws/en/security/network/classic/customer-managed-vpc&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 15 Jan 2026 07:47:52 GMT</pubDate>
    <dc:creator>emma_s</dc:creator>
    <dc:date>2026-01-15T07:47:52Z</dc:date>
    <item>
      <title>Queries Hanging Indefinitely</title>
      <link>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144104#M4736</link>
      <description>&lt;P&gt;I spun up a databricks environment on AWS via the AWS marketplace.&lt;/P&gt;&lt;P&gt;All the required infrastructure such as S3, VPC, Subnets are automatically created during the process&lt;/P&gt;&lt;P&gt;Once I get the Databricks environment up and running - I created a cluster. I attached that cluster with a notebook and tried running simple query: Show Catalogs; The query is running indefinitely and eventually timing out, If I run select 1 that is working correctly&lt;/P&gt;&lt;P&gt;I can explore the catalogs, explore the volumes if I attach serverless cluster to the notebook&lt;/P&gt;&lt;P&gt;What is wrong with the compute that I am creating?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jan 2026 00:59:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144104#M4736</guid>
      <dc:creator>Sai03</dc:creator>
      <dc:date>2026-01-15T00:59:58Z</dc:date>
    </item>
    <item>
      <title>Re: Queries Hanging Indefinitely</title>
      <link>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144120#M4737</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I believe this is happening as you haven't got the right ports open to connect between your classic compute and the UC Metatstore. When you try to select 1 it works as it doesn't need to talk to the metastore but when you do show catalogs it is trying to reach the metastore and time out. You can verify this by running the following code.&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;import subprocess
workspace_url=spark.conf.get("spark.databricks.workspaceUrl")
ports = [443, 3306, 8443, 8444,]
for port in ports:
    check_cmd = f"nc -w2 -vz $(dig +short {workspace_url} | tail -n1) {port}"
    result = subprocess.run(check_cmd, shell=True, capture_output=True, text=True)
    print(f"Port {port}:", "Success" if result.returncode == 0 else "Failure")&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp; Note in the future you will also need ports 8445-8451 open as well as the ones in the code above. If any of these fail when you run the above script then you will need to open access to these ports. More details here&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/security/network/classic/customer-managed-vpc" target="_blank"&gt;https://docs.databricks.com/aws/en/security/network/classic/customer-managed-vpc&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jan 2026 07:47:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144120#M4737</guid>
      <dc:creator>emma_s</dc:creator>
      <dc:date>2026-01-15T07:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: Queries Hanging Indefinitely</title>
      <link>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144123#M4738</link>
      <description>&lt;P&gt;Hi Emma, Thanks for your reply. I ran the code provided and from the result I could see - 8443,8444 were failure. Should I need to open these ports ?&lt;/P&gt;&lt;P&gt;Just to be clear - I used AWS Quickstart and the VPCs are created via the default CloudFormation template&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sai&lt;/P&gt;</description>
      <pubDate>Thu, 15 Jan 2026 09:10:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/queries-hanging-indefinitely/m-p/144123#M4738</guid>
      <dc:creator>Sai03</dc:creator>
      <dc:date>2026-01-15T09:10:07Z</dc:date>
    </item>
  </channel>
</rss>

