RabbitMQ - Unacked Messages not considering for scaling the pods #6494
Unanswered
Sathya-omnius
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
HI Team,
we are facing an issue that Keda is not scaling when we have unacked messages in the queue , currently we are using cloudampq which does not support any unencrypted connections i.e http so as per the Keda official documentation it is mentioned that we need to use http in order to include unacked messages as part of scaling.
could some one provide alternate solution what would be work around in order to scale the pods considering unacked messages .
error which we are getting with http:
2025-01-14T11:31:32Z ERROR scale_handler error getting scale decision {"scaledObject.Namespace": "trainer", "scaledObject.Name": "predictions-0a8f3576-1-scaledobject", "scaler": "rabbitMQScaler", "error": "error inspecting rabbitMQ: Get "[http://user:[email protected]:5671/api/queues/%2F/q-prediction.0a8f3576-d177-4ea7-887e-35bed1115756.document-classification](http://user:[email protected]:5671/api/queues/%2F/q-prediction.0a8f3576-d177-4ea7-887e-35bed1115756.document-classification%5C)": net/http: HTTP/1.x transport connection broken: malformed HTTP response "AMQP\x00\x00\t\x01""}
Beta Was this translation helpful? Give feedback.
All reactions