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: 

Jobs failing with repl error

ossinova
Contributor II

Recently my Databricks jobs have failed with the error message:

Failure starting repl. Try detaching and re-attaching the notebook.
 
java.lang.Exception: Python repl did not start in 30 seconds seconds.
	at com.databricks.backend.daemon.driver.IpykernelUtils$.startIpyKernel(JupyterDriverLocal.scala:1469)
	at com.databricks.backend.daemon.driver.JupyterDriverLocal.startPython(JupyterDriverLocal.scala:1084)
	at com.databricks.backend.daemon.driver.JupyterDriverLocal.<init>(JupyterDriverLocal.scala:624)
	at com.databricks.backend.daemon.driver.PythonDriverWrapper.instantiateDriver(DriverWrapper.scala:712)
	at com.databricks.backend.daemon.driver.DriverWrapper.setupRepl(DriverWrapper.scala:342)
	at com.databricks.backend.daemon.driver.DriverWrapper.run(DriverWrapper.scala:231)
	at java.lang.Thread.run(Thread.java:750)

The job is attached to a pool using Spot Pricing.

What is the best procedure to avoid this? Adding retry?

1 REPLY 1

Ajay-Pandey
Esteemed Contributor III

Yes, you can use re-try if still it's not resolve raise a support ticket to databricks

Ajay Kumar Pandey

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you won’t want to miss the chance to attend and share knowledge.

If there isn’t a group near you, start one and help create a community that brings people together.

Request a New Group