Hi all, I'm facing an issue regarding concurrency,...
# ask-community
q
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.
Copy code
run_coordinator:
  module: dagster.core.run_coordinator
  class: QueuedRunCoordinator
  config:
    max_concurrent_runs: 10
    tag_concurrency_limits:
      - key: "Reports"
        limit: 2
job details
Copy code
@job(
  resource_defs={"report_details": report_details.get_details},
  tags={"type": "Reports"},
)
d
Hi Qumber - "Reports" would need to be a key rather than a value for it to apply here
Copy code
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
I have tired this too, but not working.
d
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
here is the configurations, I think dagit not picking up my QueuedRunCoordinator configurations.
d
You'l need to restart dagit and your daemon to pick up changes to your dagster.yaml
q
Solved, thanks.
condagster 1