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

Think on a way to avoid triggering tasks that are disabled #1799

Closed
acelaya opened this issue Jun 3, 2023 · 0 comments · Fixed by #1801
Closed

Think on a way to avoid triggering tasks that are disabled #1799

acelaya opened this issue Jun 3, 2023 · 0 comments · Fixed by #1801
Milestone

Comments

@acelaya
Copy link
Member

acelaya commented Jun 3, 2023

Currently, Shlink has a number of background jobs and tasks that can be run with RoadRunner or openswoole.

These tasks can be enabled or disabled, but all of them are always triggered no matter what, and each one of them is responsible to immediately exit if not enabled.

This was a reasonable approach at first, but as the number of tasks grows, this is starting to become problematic, because there's a limited amount of job workers, and too many tasks can potentially block each other.

It would be good to find a way to not trigger tasks at all if they are not enabled.

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

Successfully merging a pull request may close this issue.

1 participant