The Ultimate Guide to High Availability with MariaDB

RDS MariaDB Restarted Due to Optimized Writes Storage Compatibility Issue

You are viewing an old version of this question. View the current version here.

Issue Summary: We recently encountered an unexpected restart of our Amazon RDS MariaDB instance with the following event logs:

DB instance restarted February 12, 2025, 18:34 (UTC+05:30) Binlog position from crash recovery is mysql-bin-changelog.311813 663 February 12, 2025, 18:34 (UTC+05:30) DB instance restarted February 12, 2025, 18:33 (UTC+05:30) 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 MARIADB documentation.

Environment Details: • RDS Engine: MariaDB 10.6.18 • Storage Type: gp2 • Parameter Group: Custom • Multi-AZ: Yes

Observations & Questions: 1. No recent configuration changes, but this issue has started appearing suddenly. 2. Storage type is still gp2, yet RDS is now flagging incompatibility with Optimized Writes. 3. innodb_doublewrite is ON, but we did not manually enable any Optimized Writes settings.

Has anyone faced a similar issue, or is there a workaround to prevent unexpected restarts due to this setting?

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.