Closed tunayokumus closed 2 weeks ago
@tunayokumus : This is odd. Are there differences in network configuration between the workspaces? If so, what? Also, in the same workspace, could you compare the ucx job clustter configuration with the configuration of a (job) cluster that does not fail after two hours?
Finally, does the error still persist today?
@tunayokumus Few things to check on the job that is failing.
Is there an existing issue for this?
Current Behavior
After installing the UCX to our Azure Databricks workspace the assessment job has been failing so far. At first it was only the crawl_tables task failing due to a Spark driver error. In the consequent runs more tasks started to fail. The task failures happen around 1-2 hour after the job is started.
Here are some of the error codes from the failed tasks:
crawl_tables: "The spark driver has stopped unexpectedly and is restarting. Your notebook will be automatically reattached. at com.databricks.spark.chauffeur.Chauffeur.onDriverStateChange(Chauffeur.scala:1478)"
crawl_groups: "com.databricks.backend.common.rpc.DriverStoppedException: Driver down cause: driver state change (exit code: 137)"
Expected Behavior
In another workspace the assessment job ran successfully without issues. We applied the same configuration to both workspaces when installing UCX.
Steps To Reproduce
No response
Cloud
Azure
Operating System
Linux
Version
latest via Databricks CLI
Relevant log output