https://dagster.io/ logo
Title
q

Qumber Ali

11/12/2021, 12:57 PM
Hi all, I'm facing an issue regarding concurrency, here is my dagster.yaml and jobs details where i'm setting the tag. But when I run the Dagster all the jobs starts synchronously by sensor instead of only two.
run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator
  config:
    max_concurrent_runs: 10
    tag_concurrency_limits:
      - key: "Reports"
        limit: 2
job details
@job(
  resource_defs={"report_details": report_details.get_details},
  tags={"type": "Reports"},
)
d

daniel

11/12/2021, 1:22 PM
Hi Qumber - "Reports" would need to be a key rather than a value for it to apply here
run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator
  config:
    max_concurrent_runs: 10
    tag_concurrency_limits:
      - key: "type"
        value: "Reports" 
        limit: 2
would work though i believe
q

Qumber Ali

11/12/2021, 1:23 PM
I have tired this too, but not working.
d

daniel

11/12/2021, 1:25 PM
there are a couple of troubleshooting steps here: https://docs.dagster.io/deployment/run-coordinator#troubleshooting-queued-runs - could you try those and see if they help explain what's happening?
q

Qumber Ali

11/12/2021, 1:30 PM
here is the configurations, I think dagit not picking up my QueuedRunCoordinator configurations.
d

daniel

11/12/2021, 1:42 PM
You'l need to restart dagit and your daemon to pick up changes to your dagster.yaml
q

Qumber Ali

11/12/2021, 1:51 PM
Solved, thanks.
:condagster: 1