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 documents the `MaxPendingMessagesOption` across multiple versions, showcasing its availability in various releases, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["The `MaxPendingMessagesOption` is used to define the maximum number of messages that can remain in a pending state after a publisher flushes a batch."],["This option is relevant for applications with constraints on memory resources and message capacity, allowing them to manage the pending state of messages effectively."],["`MaxPendingMessagesOption` is an alias of `std::size_t`."]]],[]]
