Geoffrin is now serving as the main database server (with memory down to 2 gigs I wasn't able to detect any errors in memtester). Ursula is now a replicated slave; if Geoffrin explodes in theory we should be able to switch back over to Ursula.
I also put the initial database onto gunther, but haven't finished setting up mysql there. Will make that a replicant too I suspect. Only 1GB of memory, but it's got the big fast raid configuration that is probably a better tradeoff if we have to use it.
At some point in the next day or so I'd like to get one or another of the faster machines to take over en.wikipedia.org and get rid of en2.
Also, if things don't fall down we can start taking down the extreme anti-slowness measures again.
-- brion vibber (brion @ pobox.com)
the HTTP links to en2 from external websites will not work anymore???
--- Brion Vibber brion@pobox.com wrote:
At some point in the next day or so I'd like to get one or another of the faster machines to take over en.wikipedia.org and get rid of en2.
__________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
On Jan 20, 2004, at 13:18, Optim wrote:
the HTTP links to en2 from external websites will not work anymore???
10 Status Code Definitions
[snip]
10.3 Redirection 3xx
This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection. Note: previous versions of this specification recommended a maximum of five redirections. Content developers should be aware that there might be clients that implement such a fixed limitation.
[snip]
10.3.2 301 Moved Permanently
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
-- brion vibber (brion @ pobox.com)
Brion Vibber wrote:
Geoffrin is now serving as the main database server (with memory down to 2 gigs I wasn't able to detect any errors in memtester).
Performance on the de:Wikipedia is currently pretty good, maybe even a bit better ;)
A lot of thanks to all who have helped!
Greetings, -asb
wikitech-l@lists.wikimedia.org