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 documents the `MaxPendingMessagesOption` across multiple versions of the Google Cloud Pub/Sub C++ client library."],["The latest release candidate version is 2.37.0-rc, with a series of prior releases, including 2.36.0, 2.35.0 and down to 2.11.0 listed."],["`MaxPendingMessagesOption` controls the maximum number of messages that can remain pending after a publisher flushes a batch, impacting memory usage and potential message rejection."],["The type alias for `MaxPendingMessagesOption` is defined as `std::size_t`, which is an unsigned integer type."]]],[]]
