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

New Solace scaler for Direct Messaging #6545

Open
alfonso-chacon opened this issue Feb 12, 2025 · 2 comments · May be fixed by #6546
Open

New Solace scaler for Direct Messaging #6545

alfonso-chacon opened this issue Feb 12, 2025 · 2 comments · May be fixed by #6546

Comments

@alfonso-chacon
Copy link

Proposal

New Solace scaler that provides the ability to scale the number of client instances automatically based upon transient load for shared subscription (message backlog, message rate)

Scaler Source

Message backlog and message rates for consumers that uses shared subscriptions

Scaling Mechanics

Scaler will collect the following metrics from a Solace PubSub+ Event Broker using SEMP:

  • D-1 queue message count length-msgs
  • Transmission rate to client (bytes) txByteRate
  • Transmission rate to client (messages) txMsgRate
  • 1-minute average transmission rate to client (bytes) averageTxByteRate
  • 1-minute average transmission rate to client (messages) averageTxMsgRate

Metrics collected will be aggregated and compared against a specified desired target

Authentication Source

Solace Basic Auth

Anything else?

No response

@JorTurFer
Copy link
Member

Hello
New scaler support is always nice! I have a question, can't this be done with the current solace scaler? If not, can we extend the current scaler to support it?

@JorTurFer JorTurFer moved this from To Triage to Proposed in Roadmap - KEDA Core Feb 13, 2025
@alfonso-chacon
Copy link
Author

Hi Jorge,

It can't be done with the current Solace Scaler as is a completely different approach. Current scaler is for Guaranteed Messaging, and it monitors a specific queue for its statistics (messages queued, spool used, message/rate) its goal is to prevent messages to build up on a physical queue.

This new Scaler is for Direct Messaging that receive messages using shared subscriptions, the metrics used here are transient (transmitted message rate, transmitted bytes rate, D-1 queue length), all this metrics exists as long as the clients are connected, its goal is to maintain client performance by managing resources in concert with inbound direct message rate using transient metrics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Proposed
Development

Successfully merging a pull request may close this issue.

2 participants