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 page provides a detailed list of versions for \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e, ranging from 2.11.0 to the latest release candidate 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e pertains to the maximum size allowed for messages that are pending after a publisher flushes a batch but have not yet been received by the service.\u003c/p\u003e\n"],["\u003cp\u003ePending message batches consume memory resources in the client and potentially in the service, with applications sometimes needing to limit the number of bytes or messages in this state.\u003c/p\u003e\n"],["\u003cp\u003eThe underlying type of \u003ccode\u003eMaxPendingBytesOption\u003c/code\u003e is specified as \u003ccode\u003estd::size_t\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
