After a publisher flushes a batch of messages the batch is (obviously) not received immediately by the service. While the batch remains pending it potentially consumes memory resources in the client (and/or the service).
Some applications may have constraints on the number of bytes and/or messages they can tolerate in this pending state, and may prefer to block or reject messages.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This page documents various versions of the `MaxPendingBytesOption` for Google Cloud Pub/Sub in C++, ranging from version 2.11.0 to the latest release candidate, 2.37.0-rc."],["`MaxPendingBytesOption` is used to manage the maximum size of pending messages in a publisher, allowing control over memory resources in the client."],["The versions listed represent different releases where this option can be implemented and utilized, with links provided for each version's documentation."],["The `MaxPendingBytesOption` type alias is represented by `std::size_t`, which represents the maximum pending message size."]]],[]]
