The English-language Wikipedia will be in _read-only mode_ for a few hours tonight (Feb 9->Feb 10) while the database structure is altered to eliminate some of the remaining performance drags before the heavy weekday traffic gets into full swing.
This will also fix the out-of-order page history bug, which was caused by a temporary workaround to the slow history problem.
The downtime window will cover roughly 04:00-08:00 UTC (UK time). For us USians, that's 8pm-midnight PST / 11pm-3am EST. Australians & others, please check http://www.wikipedia.org/wiki/Time_zone for the appropriate offset to your local time. (I'm not certain of the end time; it may run shorter, and hopefully won't run longer. It's a big database, and mass modifications take a *long* time.)
During that time the wiki should remain accessible for reading, but no one will be able to log in or make edits.
I'll also be upgrading various other languages to the current software revision; those should go relatively quickly, and will be staggered. Generally, meta, wiktionary, and Wikipedia's other languages should remain accessible for both reading and editing through the night except for some brief read-only outages.
-- brion vibber (brion @ pobox.com)
ps Tech note: I figure we should hold off on the mysql 4 upgrade until they can release a version that isn't followed within a day by a dire warning about a new bug that directly affects a type of query that we use a lot for Wikipedia. :)
In the meantime, I'm adding the inverse timestamp column which can be sorted on the index by mysql 3 (thus speeding and fixing bugs in history, contribs, & recentchangeslinked), and a random queue index column to replace the separate table and its insanely slow refilling operation.
On dim, 2003-02-09 at 12:57, Brion Vibber wrote:
The English-language Wikipedia will be in _read-only mode_ for a few hours tonight (Feb 9->Feb 10) while the database structure is altered to eliminate some of the remaining performance drags before the heavy weekday traffic gets into full swing.
This will also fix the out-of-order page history bug, which was caused by a temporary workaround to the slow history problem.
The downtime window will cover roughly 04:00-08:00 UTC (UK time). For us USians, that's 8pm-midnight PST / 11pm-3am EST. Australians & others, please check http://www.wikipedia.org/wiki/Time_zone for the appropriate offset to your local time. (I'm not certain of the end time; it may run shorter, and hopefully won't run longer. It's a big database, and mass modifications take a *long* time.)
Will run a while longer; my initial estimate left out doing a backup run first, which itself is rather slow. My apologies...
-- brion vibber (brion @ pobox.com)
On lun, 2003-02-10 at 00:01, Brion Vibber wrote:
Will run a while longer; my initial estimate left out doing a backup run first, which itself is rather slow. My apologies...
Well, if the damn thing ever finishes (which it had damn well better in the next hour or so), it should automatically kick back into read-write mode.
(I suspect there are still some tweaks to the database configuration we could make that would make these overhauls run a lot faster...)
-- brion vibber (brion @ pobox.com)