TASK-258127: New throttling options in the host scope configuration#847
Open
dkoerichbird wants to merge 3 commits into
Open
TASK-258127: New throttling options in the host scope configuration#847dkoerichbird wants to merge 3 commits into
dkoerichbird wants to merge 3 commits into
Conversation
Signed-off-by: Doug Koerich <douglas.koerich@bird.com>
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
deepakpn
requested changes
Jun 1, 2026
| This option can also be used to throttle *ecstream* connections. | ||
|
|
||
| <a name="conf.ref.outbound_throttle_connections.host_scope"></a> | ||
| ### `Outbound_Throttle_Connections` in the `host` Scope |
Contributor
There was a problem hiding this comment.
It would be helpful to clarify the fallback semantics w.r.t. same and/or different MX host preference levels, on how and when the re-selection happens when the limits are saturated (both for connection and message host throttles).
Signed-off-by: Doug Koerich <douglas.koerich@bird.com>
Signed-off-by: Doug Koerich <douglas.koerich@bird.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Documentation-only changes to Momentum config reference and changelog; no runtime or application code in the diff.
Overview
Documents TASK-258127:
outbound_throttle_messagesandoutbound_throttle_connectionscan be set inhoststanzas for per-MX-host rate limits (5.3.0 changelog entry).Docs updated: the options summary table and
ref-hostnow list both options underhost.ref-outbound-throttle-connectionsandref-outbound-throttle-messagesgain large host scope sections: additive layering with binding/domain/global throttles, a dedicated fallback chain (binding_group::binding::host→ … →host), MX spillover when saturated (aligned withmax_outbound_connections), shared buckets for regex hosts, local-only enforcement vs cluster throttle options, and (for messages) mid-session re-check behavior. Scope/See Also lines are adjusted accordingly.Reviewed by Cursor Bugbot for commit 556e20b. Bugbot is set up for automated code reviews on this repo. Configure here.