[
https://issues.apache.org/jira/browse/TS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365377#comment-15365377
]
Leif Hedstrom edited comment on TS-4642 at 7/7/16 12:23 AM:
------------------------------------------------------------
It's unfortunately not as simple as that, since not all requests should have a
parent. And some should potentially have different parents. Fwiw, we're working
on some configuration changes where we add rules to parent.config to go direct
for those (few) domains that should go direct (no parent), and then a
dest_domain=. for everything else.
Your use case also seems useful, albeit I'd argue that the settings and
configurations are not obvious :).
was (Author: zwoop):
It's unfortunately not as simple as that, since not all requests should have a
parent. And some should potentially have different parents.
Your use case also seems useful, albeit I'd argue that the settings and
configurations are not obvious :).
> Parent host healths across multiple configurations is inefficient
> -----------------------------------------------------------------
>
> Key: TS-4642
> URL: https://issues.apache.org/jira/browse/TS-4642
> Project: Traffic Server
> Issue Type: Improvement
> Components: Parent Proxy
> Reporter: Leif Hedstrom
> Assignee: John Rushford
> Fix For: sometime
>
>
> It seems that if I have multiple config lines in parent.config, where I use
> the same list of parents for multiple rules, each such rules keeps it's own
> "health" status? That means that if you repeat a line 100 times, the number
> of "failures" until marked down is 100x more than what we configured in
> records.config.
> It seems that the health and failure counts should be per host, such that
> regardless of how many times I use each host in parent.config, it'll
> consistently use the settings from records.config.
> So, I'm not 100% sure this is how things works, but if they are not, I blame
> Phil.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
