Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2024 10:24 AM
I have configured a job using `databricks.yml`
```
resources:
jobs:
my_job:
name: my_job
tasks:
- task_key: create_feature_tables
job_cluster_key: my_job_cluster
spark_python_task:
python_file: ../src/create_feature_tables.py
- task_key: evaluate_model
job_cluster_key: my_job_cluster
spark_python_task:
python_file: ../src/evaluate_model.py
job_clusters:
- job_cluster_key: my_job_cluster
new_cluster:
policy_id: ${var.job_cluster_policy}
spark_version: 15.2.x-cpu-ml-scala2.12
node_type_id: i3.xlarge
aws_attributes:
first_on_demand: 1
autoscale:
min_workers: 1
max_workers: 12
```
For some reason, the job runs on shared compute, not my_job_compute as configured in the yml file:

For some reason, the job runs on shared compute, not my_job_compute as configured in the yml file:
How can I coax Databricks to use my_job_cluster, not shared compute?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2024 11:02 PM
Hi @cm04 ,
You can try to upgrade CLI to newest version. I've seen similiar issue before and upgrading CLI was a solution back then.
Solved: Yml file replacing job cluster with all-purpose cl... - Databricks Community - 72248
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2024 06:09 AM
Thanks! Updating CLI from v .224 to v0.228 seems to have resolved the issue.