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\u003eThe latest version available is 2.37.0-rc, which represents a release candidate version of the software.\u003c/p\u003e\n"],["\u003cp\u003eThis page provides access to documentation for multiple versions of the software, ranging from 2.11.0 up to the latest release candidate.\u003c/p\u003e\n"],["\u003cp\u003eThe documentation on this page specifically covers \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e, which relates to setting constraints on pending message size within the \u003ccode\u003egoogle::cloud::pubsub\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is a configuration option to manage the maximum number of bytes a user is willing to tolerate in a pending state in memory.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is an alias of the \u003ccode\u003estd::size_t\u003c/code\u003e data type.\u003c/p\u003e\n"]]],[],null,[]]
