It wouldn't really make sense to introduce a new data structure (the
consistent hash ring code), I'll can reuse the consistent hashing algorithm
but not any associated data structures. Regarding parent selection, how did
you think they could be more consistent?
On Mon, Aug 10, 2015 at 12:10 PM, Ph
On Sun, Aug 9, 2015 at 9:10 PM Brian Geffon wrote:
> All,
> We currently support strict and timed round robin for round robin DNS
> records and I'd like to propose adding consistent hashing based DNS
> selection. We're trying to replace our current ATS -> Haproxy setup with
> only ATS and that's
All,
We currently support strict and timed round robin for round robin DNS
records and I'd like to propose adding consistent hashing based DNS
selection. We're trying to replace our current ATS -> Haproxy setup with
only ATS and that's been the motivation behind all of our recent HostDB
improvement
Github user masaori335 closed the pull request at:
https://github.com/apache/trafficserver/pull/268
---
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 feat
Github user masaori335 commented on the pull request:
https://github.com/apache/trafficserver/pull/268#issuecomment-129266420
This is merged as 1cbe7c70bf81b6ba678070670da649de510b7991.
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user maskit commented on the pull request:
https://github.com/apache/trafficserver/pull/263#issuecomment-129261728
It's in 7d63eae284d3bbc705d897639957b618fa5ce1b4
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user maskit closed the pull request at:
https://github.com/apache/trafficserver/pull/263
---
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