- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello.
The following explanation may be relevant.
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-32.html
Data and GTIDs backed up by mysqldump were inconsistent when the options --single-transaction and --set-gtid-purged=ON were both used. This was because, between the start of the transaction by mysqldump and the fetching of GTID_EXECUTED, GTIDs on the server could have increased already. With this fix, a FLUSH TABLES WITH READ LOCK is performed before fetching GTID_EXECUTED, to ensure that its value is consistent with the snapshot taken by mysqldump.
Therefore, try running the command with the option "--set-gtid-purged=OFF" as shown below.
mysqldump --single-transaction --set-gtid-purged=OFF -h {host} {schema}
Hi,
The Aurora official documentation clearly states that it is supported: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.mysqldump.html
Also, see section "Tooling" of following doc: https://d0.awsstatic.com/product-marketing/Aurora/Aurora_Export_Import_Best_Practices_v1-3.pdf
Best,
Didier
Contenus pertinents
- demandé il y a un an
- demandé il y a 3 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 ans
The stackoverflow below is for RDS MariaDB, not Aurora MySQL, but this command seems to work around it. https://stackoverflow.com/questions/75183032/mysqldump-for-aws-rds-flush-tables-error-on-linux-only