Server crash recovery

Networking & Multiplayer
#1

Hi

I’ve hit an issue already. My game sector has a list of players. I want this list persisted across SGS slices so that if one server dies, others can carry on serving that sector. However. Doing my own testing with 1 slice, if that slice dies then the server never gets the ‘player left’ message, so when the server comes back up, it all goes wrong.

What I need is a way to find out if this is the first slice to come up, so that I can wipe the player list on startup if it exists, but only for the first slice, as other slices should get the sector as the first slice sees it. Which by that point should be empty, or contain the players who have already managed to connect.

Any ideas?

Endolf

#2

Yup.

Its a known issue and on our list.

WIthin the next few versions it will put the list of logged in users away in the database, and on restart of the single stack it will go through them and send leave messages. In the case of a multi-stack system they wil lactually “watch-dog” each other for this.

We wanted this in the EA1 release and it fell out because of time and more pressing bugs.
I’ll make sure to push it to the head of the list for the next few releases as its oppeod u pas an issue in the field.

Meanwhile the only workaroudn i know (and yes its not a great one) is to clear the persistant store and start from scratch. Sorry.

#3

On thinking about it… thre is an UGLY work around in the single stack version which is to clean this up in the boot() method BUT that breaks the model and will fail misreably in a multi-stack situation.

So its better we just fix it ;D