- Newest
- Most votes
- Most comments
We have a similar issue too.
RDS (r6g, MySQL 8.0.31) created before Optimized Writes become available and currently during instance restart log shows:
"The database is using the doublewrite buffer. RDS Optimized Writes is incompatible with the storage configuration. For more information, see the RDS Optimized Writes for MYSQL documentation."
However, instance matches all conditions from the documentation and it's not possible to turn off innodb_doublewrite because it's not modifiable.
So it seems it's not possible to enable Optimized Writes for existing instance. Looks like the only way to create a new instance and move all the data (or do it with replication). Maybe it's also possible to make a snapshot and restore from it to a new instance, not yet checked.
Optimized writes is automatically enabled when the following conditions are met.
Optimize Writes will be available when the following conditions are met
- RDS for MySQL version 8.0.30 and higher.
- Use the following DB instance classes
- db.x2iedn
- db.r6i
- db.r6g
- db.r6gd
- db.r5b
- You can only modify a database to turn on RDS Optimized Writes if the database was created with a DB engine version and DB instance class that support the feature. In this case, if RDS Optimized Writes is turned off for the database, you can turn it on by setting the
rds.optimized_writesparameter toAUTO. - When you are restoring an RDS for MySQL database from a snapshot, you can only turn on RDS Optimized Writes for the database if all of the following conditions apply:
- The snapshot was created from a database that supports RDS Optimized Writes.
- The snapshot is restored to a database that supports RDS Optimized Writes.
- The restored database is associated with a parameter group with the rds.optimized_writes parameter set to AUTO.
And blue/green deployments can be used when upgrading minor MySQL versions.
Relevant content
- asked 3 months ago
- asked 7 months ago
AWS OFFICIALUpdated 3 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
This isn't correct.
Applying this configuration to an existing RDS instance that predated the release of Optimized Writes does not automatically enable it on the instance. The above criteria only apply to new instances.
Thank you for your comment. You are correct and I have revised my response.
We have the similar issue after update an exist RDS from 5.7 to 8.0.35, Is there a way to enable optimized writes on an exist updated RDS?
Any updates on this? We got a similar issue on .36 in which the instance refuses to enable optimised writes - the notice is "The database is using the doublewrite buffer. RDS Optimized Writes is incompatible with the storage configuration. For more information, see the RDS Optimized Writes for MYSQL documentation."
See https://repost.aws/questions/QUjRrTyExOTBydShz2FQBTWA/replication-lag-issue-during-and-after-upgrade-from-mysql5-7-to-mysql-8-0-36