kedacore/keda

Support message sessions in Azure Service Bus Scaler

Open

#1,479 opened on Jan 6, 2021

View on GitHubContributor guide
 (34 comments) (6 reactions) (0 assignees)Go (1,457 forks)auto 404
azurefeaturehelp wantedneeds-discussionscaler-azure-service-bus

Repository metrics

Stars
 (10,372 stars)
PR merge metrics
 (PR metrics pending)

Description

Use-Case

I have a large workload that is bound to a single session id. As a session can only be processed from a single listener (because it locks the session) scaling according to the number of messages in the queue is not... useful.

I've just added 620 messages to a queue all with the same session id and keda has scaled up the service to whopping 16 instances. But unfortunately 15 instances are doing nothing and 1 is working hard.

I'm not sure if you can interrogate the number of active sessions but if you can then...

Specification

  • Allow to specify the desired number of desired active sessions and scale based on that instead of the number of messages in a queue.

Contributor guide

Research direction
Understand Azure Service Bus session concept and how KEDA's Azure Service Bus scaler currently works. Then design a way to query the number of active sessions and scale based on that instead of message count.
Tech stack
go
Domain
backenddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesAzure Service Bus
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40