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."],[[["This webpage provides a detailed list of versions for the `MaxPendingMessagesOption` in the Google Cloud Pub/Sub C++ library, starting from version 2.11.0 up to the latest release candidate, 2.37.0-rc."],["The `MaxPendingMessagesOption` controls the maximum number of messages that can be pending after a publisher flushes a batch, potentially consuming memory resources."],["This option is used in applications with constraints on the number of bytes or messages they can have in a pending state, allowing them to block or reject messages if necessary."],["The `MaxPendingMessagesOption` is an alias of the `std::size_t` type."]]],[]]
