This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Fix max_origin_connections calculation for topology-based DSes #6807
Conversation
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
rawlinp
added
bug
Instead of only dividing the maxOriginConnections by the number of caches in the same cachegroup, divide it by the number of caches in the same tier. Closes: apache#6806
rawlinp
force-pushed
the
fix-t3c-max-origin-topology
branch
from
31dc2e9 to
eacd7b5
Compare
jpappa200
approved these changes
May 4, 2022
Contributor
jpappa200
left a comment
jpappa200
left a comment
There was a problem hiding this comment.
👍 LGTM and tests pass.
zrhoffman
pushed a commit
to zrhoffman/trafficcontrol
that referenced
this pull request
Oct 2, 2022
…e#6807) Instead of only dividing the maxOriginConnections by the number of caches in the same cachegroup, divide it by the number of caches in the same tier. Closes: apache#6806
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
Instead of only dividing the maxOriginConnections by the number of
caches in the same cachegroup, divide it by the number of caches in the
same tier.
Closes: #6806
Closes: #5427
Which Traffic Control components are affected by this PR?
t3c, formerly ORT)What is the best way to verify this PR?
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist