trafficserver-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jrushf1239k <>
Subject [GitHub] trafficserver pull request: TS-3418: Second hash ring for consiste...
Date Wed, 02 Dec 2015 17:00:46 GMT
GitHub user jrushf1239k opened a pull request:

    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 ts3418

Alternatively you can review and apply these changes as the patch at:

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 <>
Date:   2015-12-01T20:53:51Z

    Refactored Parent selection to add a Secondary hash ring.

commit 5956d1cc56aee7d81107276224b5ea4681a0c66e
Author: John J. Rushford <>
Date:   2015-12-01T21:06:04Z

    clang format.

commit efe698336a19a5860fd2e35af2ccccf9ab30f91b
Author: John J. Rushford <>
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 <>
Date:   2015-12-02T14:39:56Z

    Updated comments.

commit 4efb766d980ca2190dd530480282a3f60f85396c
Author: John J. Rushford <>
Date:   2015-12-02T14:41:10Z



If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message