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-14 UTC."],[[["\u003cp\u003eThis webpage provides a detailed list of versions for the \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e feature, ranging from the latest release candidate (2.37.0-rc) down to version 2.11.0.\u003c/p\u003e\n"],["\u003cp\u003eEach version listed links to the specific documentation for the \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e within that particular version's release of the C++ Pub/Sub library.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e controls the maximum memory that pending message batches can consume before they are sent to the service, allowing for applications to manage memory constraints and potentially block or reject messages.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is an alias of \u003ccode\u003estd::size_t\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
