Skip to content
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This repository was archived by the owner on Nov 24, 2025. It is now read-only.

t3c calculates max_origin_connections incorrectly for topology-based delivery services #6806

@rawlinp

Description

@rawlinp

This Bug Report affects these Traffic Control components:

  • Traffic Control Cache Config (t3c, formerly ORT)

Current behavior:

t3c calculates the incorrect number for a delivery service's max_origin_connections when generating header_rewrite configs. It is only using the number of caches in the same cachegroup as the given server, rather than all caches at the same tier of the topology (i.e. in a 2-tier topology -- edge+mid -- it should be using the number of all caches in the mid tier).

Expected behavior:

For DSes that use a topology, t3c should calculate a server's max_origin_connections based upon the number of all caches in the last tier (rather than only caches in that server's same cachegroup).

Steps to reproduce:

Create a topology with more than one cachegroup in the last tier. Create a DS with maxOriginConnections = 100 and assign it to that topology. Queue updates on the DS's CDN. Observe that the generated max_origin_connections option in the hdr_rw_last_<xml_id>.config file for a given cache is calculated based on the number of caches in that cachegroup rather than all cachegroups at that tier.

Metadata

Metadata

Assignees

Labels

bugsomething isn't working as intendedcache-configCache config generationhigh impactimpacts the basic function, deployment, or operation of a CDNlow difficultythe estimated level of effort to resolve this issue is low

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions