<?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: Can not open socket to local (127.0.0.1) in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/91027#M38064</link>
    <description>&lt;P&gt;Short update, I changed the script a bit by simply adding a display function just before the running the collect and this seems to work for now&lt;/P&gt;</description>
    <pubDate>Thu, 19 Sep 2024 09:19:49 GMT</pubDate>
    <dc:creator>HansAdriaans</dc:creator>
    <dc:date>2024-09-19T09:19:49Z</dc:date>
    <item>
      <title>Can not open socket to local (127.0.0.1)</title>
      <link>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/90856#M38009</link>
      <description>&lt;P&gt;Hi, I'm running a databricks pipeline hourly using python notebooks&amp;nbsp;checked out from git with on-demand compute (using&amp;nbsp;&lt;SPAN&gt;r6gd.xlarge&amp;nbsp;32GB + 4 CPU's Gravaton)&lt;/SPAN&gt;. Most of the times the pipeline runs without problems. However, sometimes the first notebook fails with the error after starting the cluster&lt;/P&gt;&lt;P&gt;```&lt;SPAN&gt;Can not open socket: ["tried to connect to ('127.0.0.1', 36349), but an error occurred: [Errno 111] Connection refused"].```&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This happens with the first interaction between the notebook and spark, running the command&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;```&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;km_per_nm &lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; (&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;spark.read.&lt;/SPAN&gt;&lt;SPAN&gt;table&lt;/SPAN&gt;&lt;SPAN&gt;(assumptions_table)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;where&lt;/SPAN&gt;&lt;SPAN&gt;(f.&lt;/SPAN&gt;&lt;SPAN&gt;col&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;item&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;) &lt;/SPAN&gt;&lt;SPAN&gt;==&lt;/SPAN&gt; &lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;km_per_nm&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;collect&lt;/SPAN&gt;&lt;SPAN&gt;()[&lt;/SPAN&gt;&lt;SPAN&gt;0&lt;/SPAN&gt;&lt;SPAN&gt;]&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;asDict&lt;/SPAN&gt;&lt;SPAN&gt;()&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;get&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;value&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;```&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;I know that this could be a sign of an OOM issue, but the result of that query is a single value from 1 row. The entire table is just 1.5 kb anyway and the driver has 32GiB of mem.&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Can you guys help me with ideas where to look at ?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Sep 2024 09:37:51 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/90856#M38009</guid>
      <dc:creator>HansAdriaans</dc:creator>
      <dc:date>2024-09-18T09:37:51Z</dc:date>
    </item>
    <item>
      <title>Re: Can not open socket to local (127.0.0.1)</title>
      <link>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/91027#M38064</link>
      <description>&lt;P&gt;Short update, I changed the script a bit by simply adding a display function just before the running the collect and this seems to work for now&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2024 09:19:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/91027#M38064</guid>
      <dc:creator>HansAdriaans</dc:creator>
      <dc:date>2024-09-19T09:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: Can not open socket to local (127.0.0.1)</title>
      <link>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/146750#M52698</link>
      <description>&lt;P&gt;HI I am facing similar error, the cluster runs 24/7 and this issue is observed for a few runs in the day. The data volume being processed is not huge but the logic that this needs to go though is complex. I do not want to include the display in production code. Please let me know your thoughts&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 17:56:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/can-not-open-socket-to-local-127-0-0-1/m-p/146750#M52698</guid>
      <dc:creator>prasad_dhongade</dc:creator>
      <dc:date>2026-02-03T17:56:27Z</dc:date>
    </item>
  </channel>
</rss>

