Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] Concurrency issue when updating databricks_job resource #4267

Open
junwei-db opened this issue Nov 22, 2024 · 0 comments
Open

[ISSUE] Concurrency issue when updating databricks_job resource #4267

junwei-db opened this issue Nov 22, 2024 · 0 comments

Comments

@junwei-db
Copy link

junwei-db commented Nov 22, 2024

Configuration

"databricks_job": {
  "routing_job_clean_room_events": {
    "continuous": {
      "pause_status": "UNPAUSED"
    },
    "control_run_state": true,
    "name": "Routing Job for clean_room_events (routing_job_clean_room_events)",
    "notification_settings": {
      "no_alert_for_canceled_runs": true,
      "no_alert_for_skipped_runs": true
    },
    "retry_on_timeout": false,
    "tags": {
      "clusterIdentifier": "routing_job",
      "clusterOwner": "eng-foresight-team"
    },
    "task": [
      {
        "existing_cluster_id": "${databricks_cluster.routing_jobs.id}",
        "max_retries": 0,
        "notebook_task": {
          "base_parameters": {},
          "notebook_path": "${databricks_notebook.routing_job.id}"
        },
        "task_key": "clean_room_events"
      }
    ]
  }
}

Expected Behavior

Modifying the job should complete successfully.

databricks_job.routing_job_clean_room_events: Modifying...

Actual Behavior

Deployed non-deterministically failed due to

│ Error: cannot update job: A concurrent request to run the continuous job is already in progress. Please wait for it to complete before issuing a new request.
│ 
│   with databricks_job.routing_job_clean_room_events,
│   on terraform.tf.json line 5918, in resource.databricks_job.routing_job_clean_room_events:
│ 5918:       },

It appears that we hit some concurrently issues when updating a job.

#3585 appears to have addressed this issue, but we are still seeing the error using the latest provider version.

Steps to Reproduce

  1. Create a job
  2. Update the job
  3. Terraform apply

Terraform and provider versions

Terraform version = 1.7
Databricks provider version = 1.56.0

Is it a regression?

Debug Output

Important Factoids

Would you like to implement a fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant