-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
RabbitMQ scaler does not support custom metricName #1975
Labels
bug
Something isn't working
Comments
rtnpro
added a commit
to rtnpro/keda
that referenced
this issue
Jul 22, 2021
rtnpro
added a commit
to rtnpro/keda
that referenced
this issue
Jul 22, 2021
Fixes kedacore#1975 Signed-off-by: Ratnadeep Debnath <rtnpro@gmail.com>
4 tasks
rtnpro
added a commit
to rtnpro/keda
that referenced
this issue
Aug 2, 2021
Fixes kedacore#1975 Signed-off-by: Ratnadeep Debnath <rtnpro@gmail.com>
rtnpro
added a commit
to rtnpro/keda
that referenced
this issue
Aug 2, 2021
Fixes kedacore#1975 Signed-off-by: Ratnadeep Debnath <rtnpro@gmail.com>
Thanks for your contribution on this @rtnpro! |
rtnpro
added a commit
to rtnpro/keda
that referenced
this issue
Aug 2, 2021
Fixes kedacore#1975 Signed-off-by: Ratnadeep Debnath <rtnpro@gmail.com>
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Report
In our use case, workers consume from multiple RabbitMQ hosts on the same
queue
name, and failover if a host goes out of service. However, without support for custommetricName
inTriggerMetadata
like other scalers likepostgresql
, triggers on the same queue, mode but different RabbitMQ hosts create duplicatemetricName
in Keda, and hence there's an error during reconciling theScaledObject
.Expected Behavior
RabbitMQ Scaler should allow & parse custom
metricName
inTriggerMetadata
, so that in the above reported use case, we can prevent duplicatemetricName
s in aScaledObject
by specifying custommetricName
.Actual Behavior
RabbitMQ scaler does not allow and parse
metricName
fromTriggerMetadata
.Steps to Reproduce the Problem
ScaledObject
for aDeployment
with multipletrigger
s using the samemode
,queue
, but on different hosts, similar to the snippet shared in the report above.Logs from KEDA operator
KEDA Version
2.3.0
Kubernetes Version
1.17
Platform
Amazon Web Services
Scaler Details
RabbitMQ
Anything else?
No response
The text was updated successfully, but these errors were encountered: