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 comprehensive 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."],["Each listed version links to the corresponding documentation for the `MaxPendingMessagesOption` struct, allowing users to explore specific features or changes."],["The `MaxPendingMessagesOption` is a configuration that limits the number of messages that can be pending (not yet acknowledged by the service) after a batch flush."],["The documentation details that the `MaxPendingMessagesOption` type is an alias for `std::size_t`, which indicates the data type used for setting the maximum pending messages."],["Managing the number of pending messages is important to control memory usage and prevent resource constraints on the client or the service."]]],[]]
