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 reference for the \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e feature within the Google Cloud Pub/Sub C++ library, detailing its function of managing the maximum size of pending messages.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version of this documentation is for the release candidate 2.37.0-rc, with other versions available from 2.36.0 down to 2.11.0.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e addresses the need for some applications to control memory usage by setting limits on the number of bytes and/or messages allowed to remain pending after a batch is flushed.\u003c/p\u003e\n"],["\u003cp\u003eThe type alias of \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is \u003ccode\u003estd::size_t\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
