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."],[[["This webpage provides a list of documentation for different versions of the `MaxPendingMessagesOption` within the Google Cloud Pub/Sub C++ client library."],["The most recent version is `2.37.0-rc`, which is designated as the latest release candidate."],["The content provides links to documentation spanning multiple previous versions, ranging from `2.36.0` down to `2.11.0`."],["`MaxPendingMessagesOption` relates to setting the maximum number of messages that can be pending, or waiting for confirmation from the service, after a batch flush."],["The `MaxPendingMessagesOption` is an alias of the `std::size_t` data type."]]],[]]
