dapr / dapr/components-contrib
Azure Service Bus Queues retry policy
- Dominant language
- Go
- Stars
- 602
- Forks
- 580
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
/area runtime
Hello,
I'm currently working with the Azure Service Bus Queues component, and I need to set a retry policy.
Unfortunately, I couldn't find a way to do it using the available metadata, as described [here](https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-azure-servicebus-queues/#spec-metadata-fields): the retries are happening, but there's no delay between them.
I tried using the [retry policies](https://docs.dapr.io/operations/resiliency/policies/#retries), but I would prefer to have the bus handle the retries instead of the sidecar; additionally, I also need the "DeliveryCount" header which doesn't get incremented if I use the sidecar's retry policies.
Contributor guide
Research direction
Start with the Azure Service Bus Queues component and its metadata fields described in the linked component documentation, then compare them with the linked resiliency retry policies. Determine how bus-side retries could include a delay and preserve the DeliveryCount header; done means the requested retry behavior is supported and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100