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

scaling up the pods based on any ActiveMQ queues instead of particular queue name (destinationName) #1527

Closed
sandeep8892 opened this issue Jan 22, 2025 · 2 comments
Labels
stale All issues that are marked as stale due to inactivity

Comments

@sandeep8892
Copy link

Currently in our application ActiveMQ queues will be created based on the endpoints created by the users so every time we cannot update the ScaledObject so is it possible to scale up the deployment based on any one of the queues reached the targetQueueSize pods should scale up

`triggers:

  • type: activemq
    metadata:
    managementEndpoint: "activemq.activemq-test:8161"
    destinationName: "testQueue"
    brokerName: "activemq_broker"
    targetQueueSize: "100"
    activationTargetQueueSize: "10"`

Instead of destinationName: "testQueue" can we do destinationName: "*"

Manually tried the api it is working fine
curl -u username:password "http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=*/QueueSize"

Image

But through the keda getting this error

2025-01-21T11:16:43Z ERROR scale_handler error getting scale decision {"scaledObject.Namespace": "backend", "scaledObject.Name": "activemq-scaledobject", "scaler": "activeMQScaler", "error": "error inspecting ActiveMQ queue size: Get "http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost,destinationType=Queue,destinationName=*/QueueSize\": context canceled"}
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScalerState
/workspace/pkg/scaling/scale_handler.go:780
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).getScaledObjectState.func1
/workspace/pkg/scaling/scale_handler.go:633
2025-01-21T11:16:43Z ERROR scaleexecutor failed to patch Objects {"scaledobject.Name": "activemq-scaledobject", "scaledObject.Namespace": "backend", "scaleTarget.Name": "workflow-services", "error": "client rate limiter Wait returned an error: context canceled"}
github.com/kedacore/keda/v2/pkg/status.TransformObject
/workspace/pkg/status/status.go:219
github.com/kedacore/keda/v2/pkg/scaling/executor.(*scaleExecutor).setCondition
/workspace/pkg/scaling/executor/scale_executor.go:111
github.com/kedacore/keda/v2/pkg/scaling/executor.(*scaleExecutor).setReadyCondition
/workspace/pkg/scaling/executor/scale_executor.go:118
github.com/kedacore/keda/v2/pkg/scaling/executor.(*scaleExecutor).RequestScale
/workspace/pkg/scaling/executor/scale_scaledobjects.go:179
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).checkScalers
/workspace/pkg/scaling/scale_handler.go:249
github.com/kedacore/keda/v2/pkg/scaling.(*scaleHandler).startScaleLoop
/workspace/pkg/scaling/scale_handler.go:182

Copy link

stale bot commented Mar 23, 2025

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Mar 23, 2025
Copy link

stale bot commented Mar 30, 2025

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Mar 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale All issues that are marked as stale due to inactivity
Projects
None yet
Development

No branches or pull requests

1 participant