When using Amazon Aurora the host must be a domain rather than an ip address because otherwise the automatic failover feature (one of the main reasons for going with Aurora) doesn't work. Also Aurora doesn't allow end users to mange innodb_checksum_algorithm, innodb_read_io_threads, or innodb_write_io_threads.

Would be nice if this could be supported.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

MustangGB created an issue. See original summary.

MustangGB’s picture

Assigned: MustangGB » Unassigned
Status: Active » Needs review
FileSize
2.74 KB

Something like this perhaps.

MustangGB’s picture

MustangGB’s picture

mikeytown2’s picture

Status: Needs review » Reviewed & tested by the community

Looks good to me; I don't have a way to test this so if this make apdqc work on Amazon Aurora 100% then I'll go ahead and commit it. Just let me know MustangGB!

MustangGB’s picture

It does allow the Status Report to go all green which was my initial aim, whether or not this constitutes working 100% or not I'm not sure as I've not delved into the inner working of the module all that much. My main use case currently is the reduction of deadlocks, so if I'm getting less (or none) or these then I'm happy.

I've only used these changes in dev so far, but have tested with both MySQL and Aurora and it hasn't broken anything. I've not tested with MariaDB, however a code review should tell you that it shouldn't be effected either.

Hope that helps, I'm happy to sit on this for a while until I get the chance to roll this out into production to see if any other issues that arise, equally if you think the inner working of the module should be able to cope fine then I also don't mind if you want to commit and go the follow-up issues route (if needs be).

mikeytown2’s picture

Status: Reviewed & tested by the community » Fixed

Patch in #3 has been committed. We can create followup issues.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.