[
https://issues.apache.org/jira/browse/TS-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368220#comment-15368220
]
Leif Hedstrom commented on TS-4642:
-----------------------------------
I thought some more on this, and I think there are at least two cases of
"failures" here:
1) A parent proxy dies completely. In such case, the child proxy ought to get a
connection failure (refused).
2) The parent proxy is talking to a bad origin, which either times out
(possibly also the parent times out), or other bad things happening.
It sounds like [~jrushford]'s case is #2. Now for #1, it'd be desirable to mark
a parent as down as soon as possible, i.e. those should be "shared" across all
parent configurations.
This gets particularly interesting if/when we implement the @parent option for
remap.config.
[~jrushford] What do you think?
> 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)
