[
https://issues.apache.org/jira/browse/TS-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197563#comment-15197563
]
ASF subversion and git services commented on TS-4115:
-----------------------------------------------------
Commit 824f2ab7bde25b9b7f8da48fdf36bc3278920444 in trafficserver's branch
refs/heads/master from John J. Rushford
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=824f2ab ]
TS-4115: Add a multi origin hierarchy to parent selection.
> Add a multi origin hierarchy to parent selection.
> -------------------------------------------------
>
> Key: TS-4115
> URL: https://issues.apache.org/jira/browse/TS-4115
> Project: Traffic Server
> Issue Type: New Feature
> Components: Core
> Reporter: John Rushford
> Assignee: John Rushford
> Priority: Minor
> Fix For: 6.2.0
>
>
> Parent Selection is currently used to create a hierarchy of cache server
> groups. It would be useful to create an origin server hierarchy through
> parent selection so that say mid tier caches could round robin requests to
> multiple origin servers possibly at different sites using round robin load
> balancing and possibly consistent hashing algorithms.
> FEATURE DESCRIPTION:
> A pull request accompanies this ticket that adds this feature to parent
> selection. A new configuration parameter "parent_is_proxy" is available in
> parent config. parent_is_proxy=true is the default and indicates that a list
> of parents and secondary_parents are the usual parent caches but, when set to
> false, it indicates that the list of parents are origin servers.
> When marked as origin servers, the server FQDN is removed from the http GET
> request so that only the relative path is in the request. Note that if
> connectivity fails to all the origins listed or all are marked down, there is
> no go direct behavior as these are the origins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
