Update on server issues

There have been two issues which have been causing FAH some series issues. I wanted to give an update.

First, networking on subnet 171.64.122.XX seems to be very slow and easily overloaded. Our diagnostics (and donor input) points to this issue being caused by a firewall on this subnet that can't handle the load. I have asked 3 different branches of our IT dept looking into this, but nobody has any fixes just yet. Getting impatient with this slow response, some time ago I requested for us to get a new network for our machines. This request is being processed. Once it's accepted, it will take a little time for them to get the new net in there (they may be able to do a VLAN, but more likely they will have to run a new physical cable, since the VLAN would still be behind the firewall). This subnet also has some of our collection servers, so this will be a big help there too once this is resolved.

Second, the current server code can get overloaded. When it does, it slows down. However, new code in the server notices this and restarts the server binary. This leads to downtime of about an hour when this happens. While, this does autofix the problem with just a little downtime, I'd like zero downtime (as would most people). I have paid a professional software house to rewrite our FAH server backend from scratch. That is almost done (it's in QA right now, with some somewhat minor issues to address). This new server code should address this issue (and other issues) with the server code, but may introduce new issues that need to be smoothed over. However, the rewrite is MUCH cleaner architected and so that will be important going forward in the future.

I just wanted to give a bump to let people know where we are. These issues aren't quick to resolve, but we are making progress. The new server code in particular will be a big help in the next 5 years of FAH, due to its rearchitecting and much cleaner code.

Comments

[6rill2000]

Thanks for the news, it's good to learn that a problem (how long to resolve it can be) is under control :)

Good news for the server code too, it's clear that sometimes rewrite from scratch is much longer but is the best to do !

[muziqaz]

So far I did not have any issues with networks :)
I guess having your own network would be better, you wouldn't be dependant from others :)

[SuperVegeta]

Wow, its amazing how hard servers are to run. It seems everyone everywhere is constantly complaining of servers. Being always on the client end, it makes me wonder why are servers so difficult, but I understand that they are.

[Adam A. Wanderer]

Sirs:
Thanks! Anything you can do is appreciated. We all realize the problems connected with hardware and software both. As long as no data is lost and serious slow downs in input/output of work units are at a minimum, there's nothing anyone or anything else could do to resolve the problems. Every donor out here is behind both you and the project.

[Saeid]

Dear Sir.
I have some idea for participating in the project. but i could not find any contact info in the web site.
please contact me via Email. My company has some solution for joining you .

regards
Saeid Poordelir

[DocJonz]

I think that with all the server dropouts/failures over the weekend (see Forum), perhaps fixes in this area should be moved higher up the priority list ......

[Anonymous]

Stats server is down.

[Creatormaster]

only 3 words: Very good news!

[Marlie]

How do I get this out of dos mode?

[Stephen Dewey]

@Marlie,

It sounds like you downloaded the console client. You should go back to the download page and download the "system tray" client instead.

In other words, if you are using Windows, you would want:

"Windows XP/2003/Vista
System tray client installer with viewer"

instead of

"Windows XP/2003/Vista
Console client only zip file (with Windows-service-install option)."

If you have further questions, please post your question in the Forum, here:

http://foldingforum.org/