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."],[[["This page provides documentation for the `MaxPendingBytesOption` in the Google Cloud Pub/Sub C++ client library."],["The latest version of `MaxPendingBytesOption` is 2.37.0-rc, with numerous older versions also documented, including those ranging from 2.36.0 back to 2.11.0."],["`MaxPendingBytesOption` manages the maximum size for pending messages, which helps applications with memory constraints in handling messages that have been flushed but not yet received."],["`MaxPendingBytesOption` is an alias of `std::size_t`."]]],[]]
