Are init scripts breaking clusters?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2023 09:11 PM - edited 11-16-2023 09:12 PM
My Jobs were running just fine, but for some reason all of a sudden they all started failing. When I looked into it I saw it was an error due to an init script error (we do use an init script).
run failed with error message
Cluster 1117-045226-lfvc8fde was terminated while waiting on it to be ready: Cluster 1117-045226-lfvc8fde is in unexpected state Terminated: INIT_SCRIPT_FAILURE(CLIENT_ERROR): instance_id:i-009209e91e8cc95e2,databricks_error_message:Cluster scoped init script /test | 290d381e-8eb4-4d6a-80d4-453d82897ecc/testinit.sh failed: Script exit status is non-zero.
What is strange is, I tried just putting in a blank init script and I still got the error above.
If I completely remove the init script, then everything works fine.
Why would a blank init script cause this error too? Is something broken in the backend?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2023 07:22 AM
Thank you for reaching out to Databricks Support.
Could you please specify the location of the initialization script you are referring to? Additionally, it would be helpful to know whether this is a global init script or one specific to a cluster. We generally recommend storing init scripts within workspace files.
Referece: https://docs.databricks.com/en/files/workspace-init-scripts.html

