Leif Hedstrom created TS-3418:
---------------------------------
Summary: Second hash ring for consistently hashed parent selection
Key: TS-3418
URL: https://issues.apache.org/jira/browse/TS-3418
Project: Traffic Server
Issue Type: New Feature
Reporter: Leif Hedstrom
It would be incredibly useful if we allowed for an (optional) second hash ring
in the consistent hashing in parent selection. Imagine a setup where you have
two set of parent proxies. A child would prefer to always use a parent <n> in
ring <A> for a set of URLs, <X>. In the case of parent <n> not being available,
instead of rehashing <X> to the surviving members of ring <A>, we could now
hash the URLs to parent <m> in ring <B>. Upon failure there, we'd then go back
and rehash on the primary ring again (<A).
This sounds complicated, but is simple in principle. Instead of immediately
rehashing content up on parent failure, have a backup pool (potentially remote)
of parents, that are likely to have the content. The idea is to minimize origin
server traffic at all cost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
