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 provides documentation for the `MaxPendingBytesOption` within the Google Cloud Pub/Sub C++ client library, across multiple versions."],["The latest version of the documentation is for version 2.37.0-rc, with links to documentation for 26 older versions, down to 2.11.0."],["`MaxPendingBytesOption` controls the maximum memory consumption for pending messages that are not yet processed by the Pub/Sub service."],["This option is used to manage the number of bytes an application is willing to tolerate in a pending state, providing control over memory resources."],["The `MaxPendingBytesOption` is an alias of the `std::size_t` type."]]],[]]
