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."],[[["This webpage provides documentation for the `MaxPendingBytesOption` within the Google Cloud Pub/Sub C++ client library, across multiple versions."],["The latest version of the documentation is for version 2.37.0-rc, with links to documentation for all versions from 2.11.0 up to 2.36.0."],["The `MaxPendingBytesOption` controls the maximum size, in bytes, of pending messages before they are sent by the publisher."],["This option helps applications manage memory usage by allowing them to set limits on the number of bytes used by messages waiting to be sent."]]],[]]
