[
https://issues.apache.org/jira/browse/TS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan M. Carroll updated TS-3999:
--------------------------------
Comment: was deleted
(was: In addition a flag will be added to the parent rule that indicates that
one of the parents is self. If this flag is present and self cannot be
identified then ATS will terminate with an appropriate warning. This would make
case (2) much safer while allowing the same configuration across multiple
machines because the flag is attached to the rule, not to a specific parent.
For example
{code}
parent="tidus:8080, yuna:8080, rikku:8080" peers=true
{code}
If the host cannot be positively identified as one of {{tidus}}, {{yuna}}, or
{{rikku}} then ATS fails out. Setting {{peers}} is allowed but not required if
{{direct}} is used because use of {{direct}} implies {{peers}}.)
> Add option to go direct for specific parent entry
> -------------------------------------------------
>
> Key: TS-3999
> URL: https://issues.apache.org/jira/browse/TS-3999
> Project: Traffic Server
> Issue Type: Improvement
> Components: Parent Proxy
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
> Labels: A
> Fix For: 7.0.0
>
>
> We want to use parenty proxying in a peer relationship so that a host can be
> both a parent and child in general but only for a specific URL. Currently
> this can be done using the CARP plugin but that can create some difficulties.
> Being able to specify that one parent in the list is actually direct to
> origin would make that much easier.
> The current suggestion is to overload the port specifier as a indicator of
> direct. For example, if you had three hosts in a pod, {{rikku}}, {{tidus}},
> and {{yuna}}, then you would configure the parent proxying on {{tidus}} as
> {code}
> "tidus:@direct, yuna:8080, rikku:8080"
> {code}
> while the configuration on {{yuna}} would be
> {code}
> "tidus:8080, yuna:@direct, rikku:8080"
> {code}.
> Similarly for {{rikku}} the port would be changed to "@direct" just for the
> "rikku" parent. I discussed several configuration options for this with
> [~dcarlin] and putting the override directly in the parent list was his
> preferred mechanism. Note that in order to have consistency between hosts in
> a pod, the list of names *must* be exactly the same across all the peers. In
> this case, it must be "tidus, yuna, rikku" for all three or loops will occur
> because of different hash seeds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
