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 webpage lists different versions of the `MaxPendingBytesOption` for Google Cloud Pub/Sub, with version 2.37.0-rc being the latest release candidate."],["The `MaxPendingBytesOption` controls the maximum size of pending messages, which are messages that have been sent but not yet received."],["The option is relevant for applications where pending message memory consumption is a concern, as it allows for control over the resources used."],["The webpage's content covers versions ranging from 2.11.0 all the way to 2.37.0-rc, providing a history of the changes to the `MaxPendingBytesOption`."],["`MaxPendingBytesOption` is an alias of `std::size_t` type, which is a standard C++ type used to represent the size of objects in memory."]]],[]]
