Skip to content

Handle ASB queue-length management throttling (pipeline detection)#5604

Draft
ramonsmits wants to merge 1 commit into
masterfrom
asb-queue-length-throttle-backoff
Draft

Handle ASB queue-length management throttling (pipeline detection)#5604
ramonsmits wants to merge 1 commit into
masterfrom
asb-queue-length-throttle-backoff

Conversation

@ramonsmits

@ramonsmits ramonsmits commented Jul 15, 2026

Copy link
Copy Markdown
Member

Detects Azure Service Bus management throttling via a PerRetry HTTP pipeline policy (observes the 429s the SDK retries away) and reactively backs off the queue-length query interval, logging a warning once per throttling episode.

One of two alternative approaches for the same issue; the other (#5605) disables the SDK retries instead.

…tling

Azure Service Bus throttles management operations (GetQueuesRuntimeProperties)
used to read queue lengths. The SDK retries the HTTP 429 responses internally, so
the throttling never surfaced as an exception and was invisible in the logs while
still showing on the namespace dashboard.

Observe the 429 responses via a PerRetry pipeline policy on the management client,
log a warning once per throttling episode, and reactively back off the query
interval (exponential up to 1 min, recovering gradually) until throttling clears.

The ServiceBusException(ServiceBusy) catch remains as a fallback for the
retries-exhausted case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Monitoring queue length checks can throttle the Azure Service Bus namespace with no log evidence

1 participant