Dapr
v1.17.6Orchestration & ManagementSingle targeted bug fix: messages arriving during graceful shutdown or pub/sub component hot-reload no longer get silently routed to dead-letter queues.
breakingAudit your dead-letter queues for silently lost messages
If you run pub/sub with dead-letter queues configured, messages diverted there during past rolling deployments or restarts were never retried — they just sat in the DLQ. Before upgrading, inspect those queues for messages that should have been processed. After upgrading to 1.17.6, plan to replay or reprocess any legitimate messages found there. Going forward, monitor DLQ depth during deployments as a health signal; a spike should now indicate actual processing failures, not shutdown timing artifacts.
enhancementUpgrade if you do rolling deployments or frequent restarts
Any team doing Kubernetes rolling updates or frequent pod restarts with pub/sub workloads should treat this as a high-priority patch. The previous behavior was silent — no errors surfaced to your app, messages just disappeared into DLQs. The fix is low-risk (a targeted behavior change in the shutdown path), so upgrading from any 1.17.x release is straightforward.
主な変更 (4)
- Messages arriving while a subscription is closing are now held (blocked) instead of immediately NACKed, letting the broker redeliver them to healthy consumers
- Fix applies to all subscription types: declarative, programmatic (HTTP and gRPC), and streaming
- Affects any scenario triggering graceful shutdown — rolling deployments, restarts, and pub/sub component hot-reloads
- In-flight messages already being processed continue to complete normally before the subscription fully closes