Today I made intermission public. As I mentioned in my post about mysql_role_swap we’ve been working hard to limit / eliminate the impact our operations Maintenance tasks have on our customer’s experience.
A few people **ticed the /tmp/hold “leftover” in mysql_role_swap script. intermission is a product of that early exploration with coordinating database Maintenance with request pausing in the web Application tier. I’ve done a good bit of **n production testing with intermission, but only limited production testing.
Last Friday we used intermission with mysql_role_swap to move Writeboard’s database to a new server. We had a single user facing exception, and we think it was likely caused by something other than the maintenance. For Friday’s Maintenance we enabled request pausing via intermission, ran mysql_role_swap, restarted the unicorn (rails) processes, and then unpaused the requests. Total Maintenance time was just a few seconds!
12-10-2012, 11:11 PM
Making Application Maintenance Fun
العرض الشجري