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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["This webpage documents different versions of the `MaxPendingBytesOption` for Google Cloud Pub/Sub's C++ client library, ranging from version 2.11.0 to 2.37.0-rc."],["The `MaxPendingBytesOption` is used to manage the maximum size of pending messages that are awaiting processing by the Pub/Sub service."],["The primary purpose of this option is to control memory usage, and optionally to reject or block messages if the limit of pending bytes is reached."],["`MaxPendingBytesOption` uses `std::size_t` as its type alias, which is an unsigned integer type."]]],[]]
