Hello!
> I am unable to provide a technical solution for that (why don't you
> delay rc messages until the replication is done?) but I am willing to
> give any feedback nescassary to help to abolish this situation where
> vandalizing something is easier than fixing it.
Our special.ops site operation team currently
is dealing with lots of issues, with main one being relieving
stockholder and user frustration levels.
Replication lag means that servers have to deal
with too much data under too much of load.
First of all, new db servers are coming soon.
They have been planned quite long time ago, and ordered at
the beginning of this month. We are running on same DB server
setup as we were running on December. This will quite increase
our database capacities, and we will be able to work with other
bottlenecks.
On the other hand, since December deployment of MediaWiki 1.4,
there has been great deal of work in software development.
MediaWiki 1.5 will have lots of cosmetic changes, some nice
features, but most important of all, it will be a bigger pleasure for
DBA to maintain the environment. It will have less data to shuffle,
less data to scan, less data to work with. What would mean better
scalability and performance. It has data rearrangement. But still,
before going live with 1.5, we'll have to take site offline (or readonly),
and restructure it.
Moreover, we're moving archive data out from our expencive DB servers
into small and neat apaches. This way we won't have to deal with large
arrays of data sitting in forgotten history and will have much more
effective DB space/cache/performance usage. In future it will be even
better if we could solve our current file storage bottleneck this way.
Extracts from p0rn movies renamed into some classic symphonies do take
quite a lot of space on our single image server. There are efforts now
here as well - we already can sync our image servers and make other nice
stuff.
With less data and more requests we will sure face other bottlenecks,
but... haha, that's what Wikimedia Operations Team is for! :)
No frustration, no vacation, total world domination! To WebServe and Protect!
Cheers,
Domas