[1.16] Add docs for subscription retry mechanism (#4826)

* Add docs for subscription retry mechanism

Signed-off-by: Albert Callarisa <albert@diagrid.io>

* Update daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md

Signed-off-by: Mark Fussell <markfussell@gmail.com>

---------

Signed-off-by: Albert Callarisa <albert@diagrid.io>
Signed-off-by: Mark Fussell <markfussell@gmail.com>
Co-authored-by: Marc Duiker <marcduiker@users.noreply.github.com>
Co-authored-by: Mark Fussell <markfussell@gmail.com>
This commit is contained in:
Albert Callarisa 2025-09-03 07:14:44 +02:00 committed by GitHub
parent 9a9ca5dfdd
commit 20ae93aa92
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 0 deletions

View File

@ -120,6 +120,12 @@ Even if the message fails to deliver, or your application crashes, Dapr attempts
All Dapr pub/sub components support the at-least-once guarantee.
### Subscription startup reliability
Dapr automatically retries failed subscription startups to improve reliability during deployment scenarios. This ensures your pub/sub applications remain resilient even when facing temporary connectivity or permission issues.
When Dapr encounters errors starting subscriptions, it shows an error message in the logs and continues to try to start the subscription.
### Consumer groups and competing consumers pattern
Dapr handles the burden of dealing with consumer groups and the competing consumers pattern. In the competing consumers pattern, multiple application instances using a single consumer group compete for the message. Dapr enforces the competing consumer pattern when replicas use the same `app-id` without explicit consumer group overrides.