cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Connect Timeout - Error when trying to run a cell

HelloDatabricks
New Contributor II

Hello everybody.

Whenever I am trying to run a simple cell I receive the following error message now:
Notebook detached. Exception when creating expectation context:
java.net.SocketTimeoutException: Connect Timeout.

After that error message the cluster is disconnected from the notebook. When I reconnect (apparently successfully) and run a cell again the same error appears after some time of waiting. Also when I navigate to my profile the values of "Display Name" and "Groups" are infinitely loading and they are never shown.

Where is the problem? I have tried many things like using multiple different browsers and creating many new clusters with different runtime versions (instead of only focusing on 12.2LTS).

I appreciate every help. Thank you very much. It did work for some time.

6 REPLIES 6

MarijaS
New Contributor III

I have the same problem this whole day. Maybe it is a databricks issue? 

toolhater
New Contributor II

Same thing. Even just a simple %fs ls times out. Tried new notebooks and computes. Any idea what is going on?

StanleyCruvinel
New Contributor II

I have no ideia what's happening.
Exception when creating execution context:
java.net.SocketTimeoutException: Connect Timeout

Wolverine
New Contributor III

I am also facing same issue from yesterday. not sure what's going on

 

MarijaS
New Contributor III

today is ok

LokeshManne
New Contributor III

@HelloDatabricks 

The error you are facing is due to not detaching the old cluster, which is terminated/auto-terminated and when you run a cluster that connected to new cluster with same name and config. Which notebook tries to connect to old cluster which is still not deleted and just terminated with new cluster under same name, which makes the notebook run under work cluster which is terminated.

LokeshManne_6-1747214072575.png

 

Solution: detach old cluster from notebook and reload the web_page, you can see only new cluster but not both at a time as below. Now attach the new cluster and run your notebook. 

LokeshManne_1-1747213679593.png

detach old cluster

LokeshManne_2-1747213709892.jpeg

reload the page, you can see only new cluster

LokeshManne_3-1747213742352.png

Now attach the new cluster and run your notebook.

LokeshManne_4-1747213756699.pngLokeshManne_5-1747213775470.png

 

 

 

 

Lokesh Manne

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now