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 lists different versions of the \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e for Google Cloud Pub/Sub, with version 2.37.0-rc being the latest release candidate.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e controls the maximum size of pending messages, which are messages that have been sent but not yet received.\u003c/p\u003e\n"],["\u003cp\u003eThe option is relevant for applications where pending message memory consumption is a concern, as it allows for control over the resources used.\u003c/p\u003e\n"],["\u003cp\u003eThe webpage's content covers versions ranging from 2.11.0 all the way to 2.37.0-rc, providing a history of the changes to the \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is an alias of \u003ccode\u003estd::size_t\u003c/code\u003e type, which is a standard C++ type used to represent the size of objects in memory.\u003c/p\u003e\n"]]],[],null,[]]
