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 page documents the `MaxPendingMessagesOption` across multiple versions of the Google Cloud Pub/Sub C++ client library."],["Version 2.37.0-rc is the latest release candidate version for this specific documentation page."],["The `MaxPendingMessagesOption` controls the maximum number of messages allowed in a pending state before they are received by the service, impacting client memory usage."],["The `MaxPendingMessagesOption` uses the type alias `std::size_t`."]]],[]]
