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 a detailed list of versions for `MaxPendingBytesOption`, a feature in the Google Cloud Pub/Sub C++ library, ranging from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `MaxPendingBytesOption` is used to limit the number of bytes that can be pending while the client awaits a response from the service after sending a batch of messages."],["This option is crucial for applications that need to manage memory consumption and control the number of messages or bytes that can be held in a pending state."],["The type alias of `MaxPendingBytesOption` is `std::size_t`, which means that the configuration value will be an unsigned integer representing the maximum size."]]],[]]
