Thanks for the explanation.
I don't think changing the current implementation would be a good idea, but
what do you think of adding another option in addition to "consistent"?
It could use the consistent hashing algorithm with peer IP addresses
instead of hostnames, as you suggested.
Not sure what
Hello!
On Wed, Feb 10, 2021 at 07:03:30PM +0200, Ari Croock wrote:
> That makes sense to me, except for the fact that "hash" (without
> "consistent") doesn't seem to be doing round-robin load balancing.
>
> Is there a reason that regular "hash" keeps returning a consistent IP? I
> could understa
Hi Maxim,
Thanks for your reply.
That makes sense to me, except for the fact that "hash" (without
"consistent") doesn't seem to be doing round-robin load balancing.
Is there a reason that regular "hash" keeps returning a consistent IP? I
could understand if both directives resulted in the behavi
Hello!
On Wed, Feb 10, 2021 at 04:21:20PM +0200, Ari Croock wrote:
> Hi all,
>
> Not sure if this belongs on the devel mailing list, I thought I would try
> to post here first.
>
>
> *Summary*
> The "hash" and "hash ... consistent" upstream directives behave differently
> when an upstream host
Hi all,
Not sure if this belongs on the devel mailing list, I thought I would try
to post here first.
*Summary*
The "hash" and "hash ... consistent" upstream directives behave differently
when an upstream hostname resolves to multiple IP addresses.
*My Use-case:*
I am using nginx as a reverse
