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."],["It includes a comprehensive version history of the `MaxPendingBytesOption`, spanning from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `MaxPendingBytesOption` sets a limit on the maximum memory that can be used by messages in a pending state."],["The webpage includes a Type Alias section, specifying that the type is an alias of `std::size_t`."],["There are potential constraints on memory usage and message count, which may require applications to either block or reject messages."]]],[]]
