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 page provides documentation for the `MaxPendingBytesOption` structure across multiple versions, ranging from 2.11.0 to 2.36.0, with a release candidate for version 2.37.0 available."],["`MaxPendingBytesOption` pertains to the maximum size allowed for messages pending after a publisher flushes a batch, but before they are fully received by the service."],["The pending messages may consume memory in either the client or service, and applications may need to limit the bytes or messages pending."],["`MaxPendingBytesOption` is defined as an alias for `std::size_t`, indicating it represents a size value."]]],[]]
