Allow activationQueueLength (SQS) to respect in-flight Messages

[claudio-vellage]

Proposal

We want to be able to tell KEDA to not kill the workers if the in-flight messages are above the activationQueueLength.

Use-Case

We have a special use-case, where we need to process a certain amount of messages, before we can eventually remove those messages from the queue. Therefore, we have a lot of in-flight messages, but unfortunately KEDA scales down our worker, before those in-flight messages are processed, leading to a lot of messages piling up in the dead letter queue. How can we achieve our goal, so that KEDA will consider the in-flight messages too for activationQueueLength or is it already the case and our issue is elsewhere? Let me know if you need more information about what exactly we are trying to achieve.

Is this a feature you are interested in implementing yourself?

No

Anything else?

No response

[tomkerkhove]

Reasonable ask, we'll need to wait for somebody to contribute this.