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-14 UTC."],[[["This webpage lists various versions of the `MaxPendingBytesOption` for Google Cloud Pub/Sub, spanning from version 2.11.0 to 2.37.0-rc, with each link pointing to the documentation for that specific version."],["The `MaxPendingBytesOption` controls the maximum memory usage by pending messages after a publisher flushes a batch, but before they are received by the service."],["Applications may use this setting to manage memory consumption and prevent the accumulation of pending messages, potentially choosing to block or reject messages when limits are approached."],["The option, `MaxPendingBytesOption` is an alias of `std::size_t`."]]],[]]
