You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/02 18:01:11 UTC
[jira] [Commented] (TS-3418) Second hash ring for consistently
hashed parent selection
[ https://issues.apache.org/jira/browse/TS-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036129#comment-15036129 ]
ASF GitHub Bot commented on TS-3418:
------------------------------------
GitHub user jrushf1239k opened a pull request:
https://github.com/apache/trafficserver/pull/359
TS-3418: Second hash ring for consistently hashed parent selection
This pull request is to add an optional secondary hash ring to parent selection and is based upon feedback from James Peach regarding pull request 321. This branch only has the secondary hash ring feature and the refactor of Parent Selection to make it possible to add a secondary hash ring.
All unit and parent selection regression tests have been checked and testing has been completed in a QA environment.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jrushf1239k/trafficserver ts3418
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/359.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #359
----
commit e04c1eea7d51aeac74d687295a7900778bcfd8c2
Author: John J. Rushford <jo...@cable.comcast.com>
Date: 2015-12-01T20:53:51Z
Refactored Parent selection to add a Secondary hash ring.
commit 5956d1cc56aee7d81107276224b5ea4681a0c66e
Author: John J. Rushford <jo...@cable.comcast.com>
Date: 2015-12-01T21:06:04Z
clang format.
commit efe698336a19a5860fd2e35af2ccccf9ab30f91b
Author: John J. Rushford <jo...@cable.comcast.com>
Date: 2015-12-02T14:28:32Z
fix cases where a parent lookup can return PARENT_FAIL when go_direct=false.
commit a5aaed418acfba6d84ea51e3fe61aeae0f9d8735
Author: John J. Rushford <jo...@cable.comcast.com>
Date: 2015-12-02T14:39:56Z
Updated comments.
commit 4efb766d980ca2190dd530480282a3f60f85396c
Author: John J. Rushford <jo...@cable.comcast.com>
Date: 2015-12-02T14:41:10Z
clang-format.
----
> 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
> Components: Parent Proxy
> Reporter: Leif Hedstrom
> Assignee: John Rushford
> Fix For: 6.1.0
>
>
> 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 upon a parent failure, we 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)