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."],[[["The webpage provides a version history for the `MaxPendingBytesOption` in the Google Cloud Pub/Sub C++ library, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["`MaxPendingBytesOption` sets a limit on the size of messages pending delivery, which is important for managing memory consumption by the client or the service."],["The `MaxPendingBytesOption` structure allows users to manage and constrain the resources used by pending batches of messages."],["The maximum size of pending messages can be limited using this, it helps to prefer to block or reject messages in some applications."],["`MaxPendingBytesOption` is defined by a type alias that refers to `std::size_t`."]]],[]]
