octoleo/gh-ost
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0b93e3697e
gh-ost/doc/rds.md
Jacob Bednarz 0b93e3697e
Add notes for aurora replication 
Due to the way aurora is architected, replication means something
slightly different to the traditional sense. This includes a work
around to use test/migrate on replica instead of only master migrations.
2017-03-24 13:44:15 +11:00

1.3 KiB
Raw Blame History

Amazon RDS# Amazon RDS

Limitations

  • No SUPER privileges.
  • gh-ost runs should be setup use [--assume-rbr][assume_rbr_docs] and use binlog_format=ROW.
  • Aurora does not allow editing of the read_only parameter. While it is defined as {TrueIfReplica}, the parameter is non-modifiable field.

Aurora

Replication

In Aurora replication, you have separate reader and writer endpoints however because the cluster shares the underlying storage layer, gh-ost will detect it is running on the master. This becomes an issue when you wish to use migrate/test on replica because you won't be able to use a single cluster in the same way you would with MySQL RDS.

To work around this, you can follow along the AWS replication between clusters documentation for Aurora with one small caveat. For the "Create a Snapshot of Your Replication Master" step, the binlog position is not available in the AWS console. You will need to issue the SQL query SHOW SLAVE STATUS or aws rds describe-events API call to get the correct position.