- Joined
- Dec 22, 2003
- Messages
- 5,755
Ok, from the info I have, a server crash goes something like this:
A zone crashes (ie midgard frontier)
All those people in the zone try to log back in
The Authentication server gets overloaded and crashes.
The auth server then has to reboot or something.
So, say that the auth server can normally cope with 400 people trying to log in at the same time. When it goes over this ( ie when theres a mass LD) it crashes.
Why not write a little script that artificially limits the Auth server to accepting 250 people? Then when it recieves too many connect's, it has a "buffer" of 150 people to over run into.
An example (assuming the overload point for the auth server is 400 and there is no artficial cap enforced.):
00:01 Zone crash
00:05 First people from booted zone try to log back in again
00:06 In the next 4 seconds 500 people try to log back in
00:10
00:11 Auth server dies
An example (assuming the overload point for the auth server is 400 and there is an artficial cap of 250 enforced.):
00:01 Zone crash
00:05 First people from booted zone try to log back in again
00:06 In the next 4 seconds 500 people try to log back in
00:08 Auth server hits cap of 250
00:10 A few odd connections get through so there are 261 people trying to log in. The server allows the extra 11 people to over-run into the buffer. However no further connections are permitted. As these 261 people log in, more people are filtered through (numbers still limited to ensure auth server dosn't die)
The result of this would be although people would perhaps take 5-10 secs longer to log on, the auth server would stay up and there would be no big problem.
I don't know if this is what happens, I dont know what happens exactly when a zone crashes.
What are peoples views on this? Would it work?
Tilda
A zone crashes (ie midgard frontier)
All those people in the zone try to log back in
The Authentication server gets overloaded and crashes.
The auth server then has to reboot or something.
So, say that the auth server can normally cope with 400 people trying to log in at the same time. When it goes over this ( ie when theres a mass LD) it crashes.
Why not write a little script that artificially limits the Auth server to accepting 250 people? Then when it recieves too many connect's, it has a "buffer" of 150 people to over run into.
An example (assuming the overload point for the auth server is 400 and there is no artficial cap enforced.):
00:01 Zone crash
00:05 First people from booted zone try to log back in again
00:06 In the next 4 seconds 500 people try to log back in
00:10
00:11 Auth server dies
An example (assuming the overload point for the auth server is 400 and there is an artficial cap of 250 enforced.):
00:01 Zone crash
00:05 First people from booted zone try to log back in again
00:06 In the next 4 seconds 500 people try to log back in
00:08 Auth server hits cap of 250
00:10 A few odd connections get through so there are 261 people trying to log in. The server allows the extra 11 people to over-run into the buffer. However no further connections are permitted. As these 261 people log in, more people are filtered through (numbers still limited to ensure auth server dosn't die)
The result of this would be although people would perhaps take 5-10 secs longer to log on, the auth server would stay up and there would be no big problem.
I don't know if this is what happens, I dont know what happens exactly when a zone crashes.
What are peoples views on this? Would it work?
Tilda