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-14 UTC."],[[["This webpage documents different versions of the `MaxPendingMessagesOption` for Google Cloud Pub/Sub in C++."],["The latest release candidate version is `2.37.0-rc`, and previous stable versions are listed down to `2.11.0`."],["`MaxPendingMessagesOption` defines a setting for the maximum number of messages that can be in a pending state after a batch flush, using `std::size_t` as an alias."],["Controlling the number of pending messages helps manage memory usage and avoid resource constraints in the client or service."]]],[]]
