Well I'd expect that when using "server chat" as per the docs:
"A domain name that resolves to several IP addresses defines multiple
servers at once."
the hash wouldn't be consistent on choosing the name, but on the server
list, because it defines multiple servers.
2017-10-09 12:23 GMT+02:00 Rom
Hi Ruben,
On Mon, Oct 09, 2017 at 11:51:54AM +0200, Ruben wrote:
> First of all thanks for your reply. But what happens if I have for example
> a hostname: test, which resolves to a randomized list of multiple ip's.
> Such that when I do:
>
> dig test
> 10.0.0.8
> 10.0.0.9
> 10.0.0.10
>
> and a
First of all thanks for your reply. But what happens if I have for example
a hostname: test, which resolves to a randomized list of multiple ip's.
Such that when I do:
dig test
10.0.0.8
10.0.0.9
10.0.0.10
and a few moments later
dig test
10.0.0.10
10.0.0.8
10.0.0.9
Is it then still consistent o
Hi Ruben,
On Mon, Oct 09, 2017 at 09:33:55AM +0200, Ruben wrote:
> I was wondering what the selection algorithm is for choosing a server in
> the upstream directive using hash. Is the selection based on the ip of the
> server or is it based on the position of the list.
>
> So if I have for exampl
I was wondering what the selection algorithm is for choosing a server in
the upstream directive using hash. Is the selection based on the ip of the
server or is it based on the position of the list.
So if I have for example the following configuration:
upstream test {
hash $arg_test;
server 1
