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

Execution Rate-limit policy #81

Open
zero88 opened this issue Oct 28, 2023 · 0 comments
Open

Execution Rate-limit policy #81

zero88 opened this issue Oct 28, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@zero88
Copy link
Owner

zero88 commented Oct 28, 2023

Is your feature request related to a problem? Please describe.

  • In the case of EventTrigger, the event can be fired in massive in a short time
  • In the case of Timing Trigger, the execution can be longer than the trigger period

Currently, schedulerx only allows running one job of a specified trigger in one moment. That is a limitation.
It is ideal to add a throttle mechanism to restrict the incoming event message for EventTrigger or in general, control the number of execution rounds of one trigger that can be run in parallel in a certain period.

Describe the solution you'd like
Provide the execution rate-limit policy interface, that

  • Supports local memory counter
  • Supports remote counter, such as the scheduler app is deployed on multiple instances in the cluster
@zero88 zero88 added this to the 2.0.0 milestone Oct 28, 2023
@zero88 zero88 self-assigned this Oct 28, 2023
@zero88 zero88 added the enhancement New feature or request label Oct 28, 2023
@zero88 zero88 changed the title Throttle policy Throttling policy Oct 29, 2023
@zero88 zero88 changed the title Throttling policy Execution Rate-limit policy Oct 31, 2023
@zero88 zero88 modified the milestones: 2.0.0, 2.1.0 Dec 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant