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 webpage provides documentation for the `MaxPendingBytesOption` struct within the Google Cloud Pub/Sub C++ library, specifically detailing its behavior across various versions."],["The latest release candidate version documented is 2.37.0-rc, with a listing of other releases from version 2.36.0 all the way down to 2.11.0."],["`MaxPendingBytesOption` controls the maximum amount of bytes allowed to be pending (not yet received by the service) after a publisher flushes a batch of messages."],["The `MaxPendingBytesOption` is an alias for `std::size_t` and it manages memory resource consumption by pending message batches."]]],[]]
