Page 1 of 1

Load-balancing

PostPosted: Sat Feb 28, 2015 7:40 pm
by Ilumini
I just saw that you released a second realmlist for other people to connect to. This can automatically be load-balanced for you by creating a round-robin DNS under a single hostname. login.nostalrius.com > 5.135.143.130 AND 178.33.122.86. This is best done with Amazon Route53 in my own experience. You can set the TTL value very low so that the IP addresses alternate back and forth as players connect.

Hope you like the idea. :)

Re: Load-balancing

PostPosted: Sat Feb 28, 2015 8:07 pm
by Shadowlurk
Are the two login server separate physical servers or are they two virtual machines on the same hardware? That would matter.

Re: Load-balancing

PostPosted: Sat Feb 28, 2015 8:09 pm
by Ilumini
Shadowlurk wrote:Are the two login server separate physical servers or are they two virtual machines on the same hardware? That would matter.



Not really. Whether they are separate or not, the IP addresses are binded to their own network interfaces and networking-wise, segregated from each other. If they weren't, the realmlist wouldn't work at all for login2 when trying to login.

Re: Load-balancing

PostPosted: Sun Mar 01, 2015 12:11 am
by r00ty
Ilumini wrote:I just saw that you released a second realmlist for other people to connect to. This can automatically be load-balanced for you by creating a round-robin DNS under a single hostname. login.nostalrius.com > 5.135.143.130 AND 178.33.122.86. This is best done with Amazon Route53 in my own experience. You can set the TTL value very low so that the IP addresses alternate back and forth as players connect.

Hope you like the idea. :)
This is of course a good idea. There's two possible problems.

The first, the current TTL on the A record could hurt it. But, so far as I can see it's 5 minutes. So, not too bad.

The second problem is that if they don't manage their own DNS now, and their current interface doesn't support multiple A records it will be a problem. At this hour, they couldn't easily change their DNS host.

As for Amazon Route 53. If you don't already have your own ability to host DNS then maybe it's a good idea. But, there's likely other services that DO support multiple A records, or of course the option of running your own server.

In short, they may have already decided to go this route, but realise it's not something they can do "tonight" let's say :)