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` across multiple versions of a software library, from version 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `MaxPendingBytesOption` relates to managing the maximum size of pending messages in a publisher's batch, which are messages that have been flushed but not yet received by the service."],["This setting is useful for applications with constraints on the amount of memory consumed by pending messages, allowing them to block or reject messages when the limit is reached."],["The underlying type for `MaxPendingBytesOption` is an alias of `std::size_t`, which is commonly used to represent the size of objects in memory."]]],[]]
