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: 

Databricks clusters unresponsive

mosayed
New Contributor

Hello everyone,

we are experiencing issues on one of our Databricks workspaces:

  • Notebooks and SQL queries are executing, but results are not returned to the UI.

  • On the screenshots you can see examples where cells in notebooks and queries in a SQL warehouse are executed successfully (clusters respond, rows are read), but the response with the data never comes back.

  • The UI stays stuck on "Fetching results”.

  • Sometimes a timeout error appears (Server error: Timed out after 60 seconds waiting for lazyLoadNotebookIfNeeded).

  • We also checked the browser developer tools: the requests are answered with HTTP 204 No Content.

This looks like one-directional communication: commands can be sent to clusters, but no data is received back in the workspace UI.

Has anyone else experienced this issue recently, and is there a known workaround?

Thanks in advance!

1 ACCEPTED SOLUTION

Accepted Solutions

mosayed
New Contributor

Thanks a lot for the quick replies!

It seems the issue was related to a faulty iPython version (or something similar inside the workspace). The problem resolved itself later the same day in the evening, and everything is working normally again now.

View solution in original post

4 REPLIES 4

Khaja_Zaffer
Contributor

Hello @mosayed

Is it possible for you to share driver logs plus

Can you change the default time out to 300 seconds 

nayan_wylde
Honored Contributor II

Can you please check if the query is in finished status and what is the time the result was returned to client.

nayan_wylde_0-1757610929270.png

 

mosayed
New Contributor

Thanks a lot for the quick replies!

It seems the issue was related to a faulty iPython version (or something similar inside the workspace). The problem resolved itself later the same day in the evening, and everything is working normally again now.

szymon_dybczak
Esteemed Contributor III

Thanks for letting us know @mosayed , could you mark your post as an answer? This help others with similar question locate solution for their problem faster.