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-04-17 UTC."],[[["This webpage provides a comprehensive list of versions for the `MaxPendingMessagesOption` in the Google Cloud Pub/Sub C++ library, spanning from version 2.11.0 to the latest release candidate 2.37.0-rc."],["The `MaxPendingMessagesOption` setting controls the maximum number of messages that can be pending after a publisher flushes a batch but before the service fully receives them."],["While in a pending state messages can consume memory, and the `MaxPendingMessagesOption` is for applications with a limited amount of resources to spare and would prefer to reject messages."],["`MaxPendingMessagesOption` is a type alias of `std::size_t`, indicating it is used to represent the size of messages."]]],[]]
