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 reference for the `MaxPendingMessagesOption` within the Google Cloud Pub/Sub C++ library, detailing its functionality and version history."],["The `MaxPendingMessagesOption` is used to set a limit on the number of messages that can be pending after a publisher flushes a batch, before they are fully processed by the service."],["There are numerous historical versions of the documentation, ranging from version 2.11.0 to 2.37.0-rc, which is the most recent release candidate."],["The option is essential for applications that have memory constraints, allowing them to manage the pending state of messages and potentially block or reject messages if the limit is exceeded."],["The `MaxPendingMessagesOption` is an alias of the `std::size_t` type."]]],[]]
