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-21 UTC."],[[["The content provides a detailed list of different versions of a software component, ranging from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["Each version entry links to specific documentation for `MaxPendingMessagesOption` within that release, located at `structgoogle_1_1cloud_1_1pubsub_1_1MaxPendingMessagesOption`."],["The `MaxPendingMessagesOption` controls the maximum number of messages that can be pending after a publisher flushes a batch, before being received by the service."],["The memory resources are consumed by pending batches of messages in the client and/or service, which can be a limiting constraint for some applications."],["`MaxPendingMessagesOption` type is defined as an alias of `std::size_t`."]]],[]]
