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 page provides a detailed list of versions for `MaxPendingBytesOption`, ranging from version 2.11.0 up to the latest release candidate, 2.37.0-rc."],["The `MaxPendingBytesOption` is used to manage the maximum size of pending messages, which are messages sent but not yet received, and this is important to limit the client memory consumption."],["This resource is specifically part of the Google Cloud Pub/Sub C++ client library, as indicated by the file paths."],["The Alias for this type is `std::size_t`, which is a type alias for the maximum size of pending messages."]]],[]]
