[
https://issues.apache.org/jira/browse/TS-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911061#comment-13911061
]
Miles Libbey commented on TS-2587:
----------------------------------
arg. completely misread the note ('You need to configure the child cache only.
No additional configuration is needed for the Traffic Server parent cache.')
Ignore the last bullet.
> Improve Hierarchical Caching documentation
> ------------------------------------------
>
> Key: TS-2587
> URL: https://issues.apache.org/jira/browse/TS-2587
> Project: Traffic Server
> Issue Type: Improvement
> Components: Documentation
> Reporter: Miles Libbey
>
> While investigating hierarchical caching, several questions arose that were
> not addressed by docs:
> - what happens when all parent caches go down? Will the children start going
> to origin themselves? [hmm, in parent.config doc, says for parent, "An
> ordered list of parent servers. If the request cannot be handled by the last
> parent server in the list, then it will be routed to the origin server"]
> - Can a parent cache accept 'normal' traffic?
> - The doc indicates that only the parent need configuration. However, that
> seems to be backwards. Seems like the child needs to know
> a) it has parents (proxy.config.http.parent_proxy_routing_enable)
> b) its parents (in parents.config) and
> c) which requests to go to parents.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
