Saw the same RDS behavior nostromo saw: was actually truly interesting. After 2 days of arguing with the RDS database I actually spun up a new local storage ins

Saw the same RDS behavior nostromo saw: was actually truly interesting. After 2 days of arguing with the RDS database I actually spun up a new local storage instance, logged in over the mysql console at a shell (which actually worked, surprisingly enough) and then found out that a single table (this is a Wordpress instance) was hung: I guess the RDS instance couldn't access the disk file for that table (it was MyISAM which I guess isn't in memory?) so any requests for that specific table hung. As it so happens that was the wp_options table, so there was no way to get past that. So I sat there with mysqldump and exported each table separately, then spun up a new MySQL instance in another AZ and then imported each table piecemeal. I then re-created the wp_options table from another dump (from an early prototype on Linode, actually) and then manually fudged the values till it all worked. That eventually worked for me.