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

Investiguate execution queue consumption by the Scheduler #7237

Open
loicmathieu opened this issue Feb 7, 2025 · 3 comments · May be fixed by #7369
Open

Investiguate execution queue consumption by the Scheduler #7237

loicmathieu opened this issue Feb 7, 2025 · 3 comments · May be fixed by #7369
Assignees
Labels
area/backend Needs backend code changes enhancement New feature or request

Comments

@loicmathieu
Copy link
Member

The Scheduler consumes the execution queue for reporting only.
It uses it to know when a trigger should have started an execution but the execution is not already started to be able to emit a WARNING.

As consuming the execution queue is costly, we may revisit this implementation and the cost/benefit balance.

@github-project-automation github-project-automation bot moved this to Backlog in Issues Feb 7, 2025
@loicmathieu loicmathieu added area/backend Needs backend code changes enhancement New feature or request labels Feb 7, 2025
@Malaydewangan09
Copy link
Contributor

Would a periodic check (e.g., every minute) for missed trigger executions be acceptable instead of continuous queue consumption? This could significantly reduce the system load while still maintaining the warning functionality.

@loicmathieu
Copy link
Member Author

We need to discuss this internally before to know what we want to do.
We may remove it or check it periodically.

@Malaydewangan09
Copy link
Contributor

Okay @loicmathieu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend Needs backend code changes enhancement New feature or request
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

2 participants