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

Weighted triggers when using multiple triggers for the same scale target #5395

Closed
hitsub2 opened this issue Jan 18, 2024 · 3 comments
Closed
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity

Comments

@hitsub2
Copy link

hitsub2 commented Jan 18, 2024

Proposal

Followed the best pratice of "Using multiple triggers for the same scale target", that would be great if weight trigger is supported. With weight trigger, we can set one trigger's activationThreshold to 0 with low priority of weight, and another trigger(based on application qps) has higher activationThreshold and weight.

When the scale from 0, the low priority of weight trigger is activeted and scale up as needed.

Use-Case

There is a scenario that we want to scale from 0 based the application of qps.When scale to 0, the trigger based on qps or any other application's internal metrics can not be scaled up.

Is this a feature you are interested in implementing yourself?

No

Anything else?

a disccusion related: #1840

@hitsub2 hitsub2 added feature-request All issues for new features that have not been committed to needs-discussion labels Jan 18, 2024
@JorTurFer
Copy link
Member

Hello,
I don't see your user case. Currently, if any scaler is active, the workload is scaled from 0, so you could scale to 0 if there isn't any active scaler and scale from 0 if there is any scaler active.
If you need more complexity, you can evaluate scaling modifiers: https://keda.sh/docs/2.13/concepts/scaling-deployments/#scaling-modifiers-experimental
Using it, you could write your own formula to fit your scenario.

Given that, HTTP scaling is quite different and you need to take into account other factors like holding the request for cold starts and so on.

Copy link

stale bot commented Mar 21, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Mar 21, 2024
Copy link

stale bot commented Mar 30, 2024

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Mar 30, 2024
@github-project-automation github-project-automation bot moved this from To Triage to Ready To Ship in Roadmap - KEDA Core Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request All issues for new features that have not been committed to needs-discussion stale All issues that are marked as stale due to inactivity
Projects
Archived in project
Development

No branches or pull requests

2 participants