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 documentation for the `MaxPendingBytesOption` across multiple versions of a C++ library, specifically for Google Cloud Pub/Sub."],["The latest version documented is `2.37.0-rc`, with a history of versions going back to `2.11.0`, each linking to their corresponding `MaxPendingBytesOption` documentation."],["`MaxPendingBytesOption` relates to the maximum number of bytes a publisher allows for messages that are pending and not yet received by the service, which is crucial for managing memory consumption and message flow control."],["The type alias for `MaxPendingBytesOption` is `std::size_t`, indicating that it represents a size value."]]],[]]
