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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["The webpage provides a comprehensive list of versions for a C++ Pub/Sub library, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["Each version listed includes a link to the documentation for the `MaxPendingBytesOption` struct within that specific release, which is a parameter that sets the maximum amount of pending data for the application."],["The `MaxPendingBytesOption` documentation describes the maximum size for pending messages, which is important for applications with constraints on memory resources due to messages not being received immediately."],["`MaxPendingBytesOption` uses `std::size_t` as the type alias for the parameter, representing a size-based type."]]],[]]
