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 for the `MaxPendingMessagesOption`, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["This documentation pertains to the `MaxPendingMessagesOption` within the Google Cloud Pub/Sub C++ library."],["The `MaxPendingMessagesOption` defines the maximum number of messages that can be pending after a batch is flushed, and not immediately received by the service, which could impact memory usage."],["The `MaxPendingMessagesOption` is an alias of `std::size_t`."],["Applications may use this feature to manage memory constraints by setting limits on the number of pending messages."]]],[]]
