Skip to content

MongoDB does not trigger scaling #6621

Discussion options

You must be logged in to vote

I think I figured this out and I'd like to share what I learned.

My confusion was with the queueValue. My objective was to start scaling when the { "status": "waiting" } query in MongoDB returned one or more documents. However, it appears that KEDA looks at this value and starts scaling after the number of returned documents is greater than queueValue (which, in this case, means 2 or greater). Also, unfortunately, setting queryValue to 0 does not work either, presumably because of how this value is used in calculations.

I'm new to k8s and KEDA so missing the above context made the job confusing. Eventually, I came across a solution that involves using scalingModifiers to achieve what I wa…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by dmitrizzle
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant