> On Aug 9, 2015, at 8:08 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'
How is this different from the current (default) client IP hashing? Mainly that
you can select different source data for the hash?
On Monday, August 10, 2015 6:28 AM, Phil Sorber wrote:
On Sun, Aug 9, 2015 at 11:18 PM Brian Geffon wrote:
> It wouldn't really make sense to introdu
On Sun, Aug 9, 2015 at 11:18 PM Brian Geffon wrote:
> 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 c
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
