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 webpage provides a comprehensive list of versions for \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e, 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 its respective documentation page for \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e within the Google Cloud Pub/Sub C++ library.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e controls the maximum number of bytes that can be pending (not yet acknowledged by the server) for message batches, allowing applications to manage client-side memory usage.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003estd::size_t\u003c/code\u003e is the Alias of the type that is used to represent the MaxPendingBytesOption.\u003c/p\u003e\n"]]],[],null,[]]
