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

Support multiple queues at the IBMMQ scaler #6181

Open
rickbrouwer opened this issue Sep 23, 2024 · 0 comments · May be fixed by #6182 or kedacore/keda-docs#1473
Open

Support multiple queues at the IBMMQ scaler #6181

rickbrouwer opened this issue Sep 23, 2024 · 0 comments · May be fixed by #6182 or kedacore/keda-docs#1473
Labels
feature-request All issues for new features that have not been committed to needs-discussion

Comments

@rickbrouwer
Copy link
Contributor

rickbrouwer commented Sep 23, 2024

Proposal

At the moment you can offer one queue to the ibmmq trigger. I want to change the queueName parameter so that it accepts multiple queues (comma (,) separated). The code will have to be changed to request the current depth per queue and only use the current depth from the queue with the most messages.

Use-Case

Our applications work with a lot of queues. Whether the application needs to scale does not depend on 1 queue. I know it is possible to set multiple triggers, but in our case that will be a lot. Also, multiple connections are set up which is unnecessary.

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

Although you can specify multiple queues, I leave the parameter name the same (queueName) so that everything continues to work properly. But queueNames is also supported.

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
Projects
Status: To Triage
1 participant