Skip to content

pubsub: exactly-once delivery should wait for the receipt modAck to succeed before proceeding #7585

@hongalex

Description

@hongalex

The current behavior is that the receipt modAck is "fire and forget", much like non-EOD receipt modAcks.

However, any delivery to the client logic should block on a successful receipt modAck. If the receipt modAck fails with a permanent error, we should not send the message to the client and not even log it. If it's a temporary failure, it should be retried.

Metadata

Metadata

Assignees

Labels

api: pubsubIssues related to the Pub/Sub API.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions