On Monday, 28th February 2011, between 9:00 and 9:30 AM UTC a maintenance of Wikidot service is planned.
We will upgrade database software (to PostgreSQL 9.0) and hardware. The planned down-time is no more than 5 minutes. The upgrade should improve both performance and stability for our backend services.
The new hardware features twice as much SSD disks (in ravishingly fast RAID-0 configuration), twice as much RAM and twice as much CPU power. This is a massive upgrade and we expect the database to literally gain super-powers. The disk read/write speed is astonishing 800/480 MB/s accordingly!
The PostgreSQL upgrade was planned a few months ago and its main purpose is to enable maintenance-free replication. It simplifies administrative tasks (such as altering database schema) that require complex manual procedures when using other replication tools. Also setting up replication and adding more database replicas are simpler tasks. This makes the data safer as the system is less prone to human mistake.
Maintenance and upgrades to Wikidot's backbone are usually transparent to our users, because there are no interface changes or new features introduced, but all these behind-the-scene operations are critical for day-to-day operation, and are reflected in overall Wikidot stability and reliability, which we are very proud of.
The photo comes from Flickr
UPDATE: the upgrade is done. Wikidot was not writable for about 10 minutes. This was not planned and due to our mistake. The problem was the sequences were not replicated so no new records could be saved into the database. Everything should work well now. Just a note: using the new replication, the whole database (including schema, table data, indexes and sequences) is replicated so this scenario should never happen again.
UPDATE2: Due to the upgrade, the "create account" code stopped working. We will fix the problem soon :-).
UPDATE3: Account creation works now. This was due to PostgreSQL change in representing values of bytea type. The solution was to tweak the configuration file of PostgreSQL to work as previously.
So, basically, wikidot is faster, safer, and awesomer? Yeah, I can live with 5 minutes of downtime for that.
@graphmastur: From what I see, if the whole process runs smoothly, there should be almost no interruption (“[…] disable write access to the database only for a few seconds to be sure […]”)..
Kenneth Tsang (@jxeeno)
Hope this all goes well !
Service is my success. My webtips:www.blender.org (Open source), Wikidot-Handbook.
Sie können fragen und mitwirken in der deutschsprachigen » User-Gemeinschaft für WikidotNutzer oder
im deutschen » Wikidot Handbuch ?
I had to be the one trying to post updates and wondering what on earth was happening!! All work now.
I really appreciate your transparent communication approach when it comes to upgrades.
5 minutes downtime for a major backend make-overs strikes me as a pretty good trade-off.
///
bergholt
It always goes wrong, but keeping downtime to 10 minutes, and then tracking down the remaining problems in not much longer, is highly commendable. You've got a good team there.
I think wikidot needs keep up with pop up options, after disabling pop-up feature a lof of members from my site is ingoring a lot of PMs due to pop-up anymore.