gehen bei euch auch die wu\'s so schlecht weg ???
gruß reiner
Nickles - Team Seti 1.753 Themen, 10.321 Beiträge
Grüsse
Bob
December 6, 2005 - 04:30 UTC
With the influx of new users, bottlenecks were bound to happen. A couple nights ago we started dropping connections on the upload/download server (kryten). This server was also serving the new BOINC core client downloads. We immediately moved the client downloads onto the campus network which was ugly, as this added about 20 Mbit/sec of traffic onto the regular campus network.
On Monday morning we fixed this by making the secondary web server (penguin) the BOINC client download server. In its former life penguin was the BOINC upload/download server so it already had the plumbing and hardware to be on the Cogent network. So without much ado, we were able to move the core client downloads off the campus net. But what about the secondary web server? Well, another Sun D220R (kosh) wasn't doing very much at the time, so we plopped apache/php on that and made it the backup web server. Some people might be getting failed connections to our home page as DNS maps need a while to propogate throughout the internet.
Meanwhile, we were still dropping connections on kryten. At first we thought this was due to the upload directories (physically attached to kryten) getting too large, as the assimilators were backing up (and they only read files in the upload dirs). Upon checking half the files in upload were "antiques," still leftover from server issues way back in August. We will delete these files in good time. We increased the ufs directory cache parameters on kryten but this didn't help at all. So our current woes must lie in the download directories (kept on a separate server) or some other bottleneck further down the pike we haven't discovered yet.
And while all this was being diagnosed and treated we actually started the master science database merge. This is why most of the backend services are disabled, and will remain off until the first half of the merge is done (about 2 days from now). We hope the results-to-send queue lasts us through this first part. Having these back-end services off is actually helping kryten catch up on its backlog of work to upload/results to download.
More to come as we discover more about current server issues and progress further with the database merge...
Falls noch nicht bekannt: Server Status
Hier sieht man am ehesten, wo es in Berkeley klemmt.