Kamal Aboul-Hosn

I don't think we need a grpc option here. I think we just need to make sure batches of modacks don't exceed the size limit.

Yeah, this definitely sounds like the issue where the publisher is overwhelmed and as a result, there are timeouts on publish, resulting in many reattempted publishes. Some type of flow...

So there is no such thing as publisher-side flow control for cloud that would help the user here. We are in the process of adding publisher flow control to our...

@flunderpero There is currently a known issue in the Pub/Sub service that is causing the 15s delay. The change that caused the issue is being rolled back right now. This...

@ChrisWestcottUK The release notes for the server only track significant API/region availability/feature availability changes, not every server change that is made. There is no public tracking for all of these...

The Pub/Sub service is designed to scale to gigabytes per second, so it should be able to handle a full production message volume. We have a [blog post](https://cloud.google.com/blog/products/data-analytics/testing-cloud-pubsub-clients-to-maximize-streaming-performance) about the...

As @mukund-ananthu mentions we do have this in other languages and so in order to provide a consistent experience to customers, it seems like we should have this feature in...

This is all in the auto-generated layer and retry behavior is governed by gax, not by the Pub/Sub client library. Transferring issue to the gax repo.

`setMetadata` is the correct method to use.

We have not been able to find a general way to approach debugging these problems, but instead have required customer-specific investigations around their setup. Please enter a support case with...