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 document lists various versions of the `MaxPendingBytesOption` for the Google Cloud Pub/Sub C++ library, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["The `MaxPendingBytesOption` pertains to the maximum size allowed for messages pending delivery after a batch flush, which can consume memory resources in both the client and the service."],["This option is important for applications with constraints on the memory used by pending messages, enabling them to block or reject new messages to avoid exceeding resource limitations."],["The type alias for `MaxPendingBytesOption` is `std::size_t`, indicating that it represents a size or count."]]],[]]
