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-14 UTC."],[[["The content provides a list of different versions of a software component, specifically related to Google Cloud Pub/Sub's `MaxPendingBytesOption`."],["Version 2.37.0-rc is identified as the latest release candidate, while 2.16.0 is mentioned as the current version, with numerous other version releases listed."],["The documentation concerns managing pending message size, highlighting memory resource consumption by batches not immediately received by the service, which can be problematic for some applications."],["`MaxPendingBytesOption`'s alias type is `std::size_t`."]]],[]]
