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.

For a Regional Delivery Service, MaxOriginConnections should only be divided among Servers within a single Cache Group #7097

@zrhoffman

Description

@zrhoffman

This Feature Request affects these Traffic Control components:

Description

The MaxOriginConnections property of a Delivery Service determines how many connections to the origin can be made, across all caches in child Cache Groups of the Origin Cache Groups. The max origin connections per cache is computed as that MaxOriginConnections value divided by the number of caches in child Cache Group of the Origin Cache Group:

maxOriginConnectionsPerServer := int(math.Round(float64(*ds.MaxOriginConnections) / float64(numLastTierServers)))

However, if a Delivery Service is only intended to be used in a specific Region, despite that Delivery Service having Cache Groups outside of that region, the computed maxOriginConnectionsPerServer value is lowered when more caches exist outside of that region, which is undesirable. In the case of a Regional Delivery Service, the maxOriginConnectionsPerServer should only divide MaxOriginConnections among caches within a given cache's own Cache Group.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Traffic Opsrelated to Traffic OpsTraffic Portal v1related to Traffic Portal version 1Traffic Portal v2Related to the experimental Traffic Portal version 2cache-configCache config generationnew featureA new feature, capability or behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions