Using RDS with slow_log enabled and encountering this error:
mysql> select * from slow_log;
ERROR 1194 (HY000): Table ‘slow_log’ is marked as crashed and should be repaired
mysql> CALL mysql.rds_rotate_slow_log;
If the same error happens when general_log is enabled, we can use:
mysql> CALL mysql.rds_rotate_general_log;
These two commands are needed to be run periodically (assuming slow_log and general_log are enabled). If the logs are getting bigger, it may affects performance of the RDS instance.
The most awaited feature of RDS for DB replication.
“We are excited to announce the release of Read Replicas, a new feature that makes it even easier to scale MySQL database deployments to meet the performance demands of high-traffic web applications. You can now create one or more replicas of a given source DB Instance and serve incoming read traffic from multiple copies of your data. This new database deployment option enables you to elastically scale out beyond the capacity of a single DB Instance for read-heavy database workloads. In conjunction with the release of Read Replicas, we are also announcing lower prices for High Memory DB Instance classes.” –Amazon
I’m getting ready to scale DB read access using RDS. 😉