Allow better flow control for push subscriptions [384042072]

Assigned

Feature Request

Status Update

No update yet.

Description

ab...@google.com

created issue #1

Dec 13, 2024 05:50PM

Pull subscribers have options to limit the number of outstanding messages or bytes. However, push subscriptions have no such options. It would be helpful to be able to limit the number of outstanding messages or bytes in order to prevent subscribe side overload. Push's backoff mechanism helps, but with an bursty workload, endpoint can get overloaded very quickly and messages redelivered multiple times, e.g., when CloudRun returns 429 errors.

Comments

va...@google.com <va...@google.com> Dec 16, 2024 06:30AM

Assigned to ar...@google.com.

ar...@google.com <ar...@google.com> #2Dec 17, 2024 07:02AM

Reassigned to gc...@google.com.

Hello,

Thank you for reaching out to us with your request.

We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.

We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the Issue Tracker providing a detailed description of your issue.

Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.

Issue 384042072

Description

Issue summary

Comments

va...@google.com <va...@google.com> Dec 16, 2024 06:30AM

ar...@google.com <ar...@google.com> #2Dec 17, 2024 07:02AM

Add comment

Issue metadata