<?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 Serverless Compute connectivity issues with .com.br domains vs. Classic Clusters Spark hangs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/serverless-compute-connectivity-issues-with-com-br-domains-vs/m-p/156856#M54486</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm facing two specific issues in my Databricks Premium workspace (AWS - sa-east-1).&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Serverless Connectivity Issue:&lt;/STRONG&gt; When using Serverless compute, I can successfully call APIs ending in .com, but calls to .com.br domains fail with connection/DNS errors. The exact same code works fine when running on a Classic Cluster.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;VPC Setup:&lt;/STRONG&gt; Custom VPC with Unity Catalog enabled.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Security Groups:&lt;/STRONG&gt; Outbound rules are open for port 443 (0.0.0.0/0).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt; It feels like a DNS resolution or Egress filtering issue specific to Serverless.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Classic Cluster Spark Hang:&lt;/STRONG&gt; On the other hand, when I switch to a Classic Cluster to bypass the connectivity issue, any Spark command (e.g., spark.read or simple transformations) hangs indefinitely without starting the job.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Has anyone experienced this specific behavior where Serverless ignores certain TLDs or where Spark fails to initialize on Classic Clusters in the same VPC?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;BR /&gt;&lt;BR /&gt;(pt-br)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Olá pessoal,&lt;/P&gt;&lt;P&gt;Estou enfrentando dois problemas distintos no meu workspace Premium (AWS - região sa-east-1):&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Conectividade no Serverless:&lt;/STRONG&gt; Não consigo consumir APIs que terminam em .com.br usando Serverless compute. Se a API for .com, funciona normalmente. O mesmo código funciona em um Cluster Clássico, o que sugere que o Serverless está lidando com o DNS ou com a saída de rede de forma diferente.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Já verifiquei os Security Groups e a porta 443 está aberta para 0.0.0.0/0.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Spark "carregando infinitamente" no Cluster:&lt;/STRONG&gt; Para contornar o problema acima, tentei usar um Cluster comum. O código de requisição API funciona, mas qualquer comando Spark (como ler um dataframe ou um simples count) fica processando infinitamente e não inicia o job.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Alguém já passou por algo parecido ou sabe se existe alguma configuração de VPC/Unity Catalog que possa estar causando esse conflito entre o tipo de computação e a resolução de domínios?&lt;/P&gt;&lt;P&gt;Obrigado!&lt;/P&gt;</description>
    <pubDate>Wed, 13 May 2026 19:12:59 GMT</pubDate>
    <dc:creator>ThiagoRosetti</dc:creator>
    <dc:date>2026-05-13T19:12:59Z</dc:date>
    <item>
      <title>Serverless Compute connectivity issues with .com.br domains vs. Classic Clusters Spark hangs</title>
      <link>https://community.databricks.com/t5/data-engineering/serverless-compute-connectivity-issues-with-com-br-domains-vs/m-p/156856#M54486</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm facing two specific issues in my Databricks Premium workspace (AWS - sa-east-1).&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Serverless Connectivity Issue:&lt;/STRONG&gt; When using Serverless compute, I can successfully call APIs ending in .com, but calls to .com.br domains fail with connection/DNS errors. The exact same code works fine when running on a Classic Cluster.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;VPC Setup:&lt;/STRONG&gt; Custom VPC with Unity Catalog enabled.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Security Groups:&lt;/STRONG&gt; Outbound rules are open for port 443 (0.0.0.0/0).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt; It feels like a DNS resolution or Egress filtering issue specific to Serverless.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Classic Cluster Spark Hang:&lt;/STRONG&gt; On the other hand, when I switch to a Classic Cluster to bypass the connectivity issue, any Spark command (e.g., spark.read or simple transformations) hangs indefinitely without starting the job.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Has anyone experienced this specific behavior where Serverless ignores certain TLDs or where Spark fails to initialize on Classic Clusters in the same VPC?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;BR /&gt;&lt;BR /&gt;(pt-br)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Olá pessoal,&lt;/P&gt;&lt;P&gt;Estou enfrentando dois problemas distintos no meu workspace Premium (AWS - região sa-east-1):&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Conectividade no Serverless:&lt;/STRONG&gt; Não consigo consumir APIs que terminam em .com.br usando Serverless compute. Se a API for .com, funciona normalmente. O mesmo código funciona em um Cluster Clássico, o que sugere que o Serverless está lidando com o DNS ou com a saída de rede de forma diferente.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Já verifiquei os Security Groups e a porta 443 está aberta para 0.0.0.0/0.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Spark "carregando infinitamente" no Cluster:&lt;/STRONG&gt; Para contornar o problema acima, tentei usar um Cluster comum. O código de requisição API funciona, mas qualquer comando Spark (como ler um dataframe ou um simples count) fica processando infinitamente e não inicia o job.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Alguém já passou por algo parecido ou sabe se existe alguma configuração de VPC/Unity Catalog que possa estar causando esse conflito entre o tipo de computação e a resolução de domínios?&lt;/P&gt;&lt;P&gt;Obrigado!&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2026 19:12:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/serverless-compute-connectivity-issues-with-com-br-domains-vs/m-p/156856#M54486</guid>
      <dc:creator>ThiagoRosetti</dc:creator>
      <dc:date>2026-05-13T19:12:59Z</dc:date>
    </item>
  </channel>
</rss>

