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

Support for limit run option to avoid delay tasks that previous not finished #254

Open
softrebel opened this issue Jul 22, 2023 · 0 comments

Comments

@softrebel
Copy link

Hi,
We are using redbeat in production and manage periodic task dynamically inside tasks. Some of tasks must be send periodically and run one task instance at once. In default, tasks send from redbeat to celery, these are been queued and not applied immediately. This behavior causes some error and manipulated result in our project. We check available solutions to fix our issue and come up with these:

  1. add "max running number" in Entry meta keys and check number of running task in reschedule method
  2. add expires argument in _maybe_due_kwargs and pass argument in "maybe_due" method.

Are these solutions are ok in redbeat?
If its ok, please let me to develop these features in redbeat.

Thanks.

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