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

concurrency per shedule not working as expected #27978

Open
benoitsdm opened this issue Feb 21, 2025 · 0 comments
Open

concurrency per shedule not working as expected #27978

benoitsdm opened this issue Feb 21, 2025 · 0 comments
Labels
type: bug Something isn't working

Comments

@benoitsdm
Copy link

benoitsdm commented Feb 21, 2025

What's the issue?

I have set the following concurrency settings:

  • key: dagster/schedule_name
    limit: 20
    value:
    applyLimitPerUniqueValue: true

But all the 120 partitions of my schedule are run at the same time

What did you expect to happen?

I expected that there were only 20 job run per schedule and the others were queued.

How to reproduce?

No response

Dagster version

1.10.1

Deployment type

Dagster Helm chart

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

@benoitsdm benoitsdm added the type: bug Something isn't working label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant