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-05 UTC."],[[["This webpage provides a detailed list of Google Cloud Pub/Sub C++ client library versions, ranging from the latest release candidate (2.37.0-rc) down to version 2.11.0."],["Each version listed links to the `MaxPendingBytesOption` documentation, which is related to setting a maximum size for pending messages in the client, specifically within the `google::cloud::pubsub` namespace."],["The `MaxPendingBytesOption` feature allows applications to manage memory consumption by limiting the number of bytes or messages in a pending state after a publisher flushes a batch."],["`MaxPendingBytesOption` is a type alias of `std::size_t`."]]],[]]
