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."],[[["The page provides a detailed list of versions for `MaxPendingBytesOption`, ranging from 2.11.0 to the latest release candidate 2.37.0-rc."],["`MaxPendingBytesOption` pertains to the maximum size allowed for messages that are pending after a publisher flushes a batch but have not yet been received by the service."],["Pending message batches consume memory resources in the client and potentially in the service, with applications sometimes needing to limit the number of bytes or messages in this state."],["The underlying type of `MaxPendingBytesOption` is specified as `std::size_t`."]]],[]]
