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 page provides documentation for the \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e structure across multiple versions, ranging from 2.11.0 to 2.36.0, with a release candidate for version 2.37.0 available.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e pertains to the maximum size allowed for messages pending after a publisher flushes a batch, but before they are fully received by the service.\u003c/p\u003e\n"],["\u003cp\u003eThe pending messages may consume memory in either the client or service, and applications may need to limit the bytes or messages pending.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is defined as an alias for \u003ccode\u003estd::size_t\u003c/code\u003e, indicating it represents a size value.\u003c/p\u003e\n"]]],[],null,[]]
