Waits until the request can be made without exceeding the limit.
This might be appropriate in batch-processing, where latencies of individual requests are
not important.
Ignore
Disables flow-control.
This is provided mainly for debugging and not recommended for production use. Having too
many requests in-flight might cause RPCs to fail due to congested network or the computer to
run out of memory due to excessive buffering, etc.
ThrowException
Throws MaxOutstandingElementCountReachedException or MaxOutstandingRequestBytesReachedException.
This might be appropriate in interactive scenarios. For example, a web server might catch
these exceptions and report to the user that the system is overloaded and that the user could
try again later. It could also be useful in applications that implement custom rate-limiting
logic.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["This webpage provides documentation for the `FlowController.LimitExceededBehavior` enum in the Google API Client Library for Java (gax), spanning versions from 2.2 to 2.63.1."],["The `FlowController.LimitExceededBehavior` enum defines how `FlowController` should handle situations where flow control limits are surpassed, offering options like `Block`, `Ignore`, and `ThrowException`."],["The `Block` behavior will pause until the request can be made within the limits, and is most appropriate for batch processing, where individual request latencies are not important."],["The `Ignore` behavior disables flow control, which is primarily intended for debugging purposes and not recommended for use in production."],["The `ThrowException` behavior will trigger either `MaxOutstandingElementCountReachedException` or `MaxOutstandingRequestBytesReachedException`, making it ideal for interactive scenarios or applications that use their own custom rate limiting."]]],[]]
