Why is my Amazon Aurora DB instance in an incompatible parameter status?
3 minute read
I have an Amazon Aurora DB instance that's in an incompatible-parameters status. Why is my DB instance in an incompatible-parameter status, and how can I resolve this issue?
The incompatible-parameters status occurs when a parameter in the associated parameter group has a value that isn't compatible with your engine version. Or, the value isn't compatible with the current DB instance class and size.
A DB instance might be in the incompatible-parameters state for one of these reasons:
The sum of memory used by parameters in the cluster and the instance parameter groups exceeds the available memory on the instance.
The database engine is incompatible with one or more of the parameter settings in the custom DB parameter group.
The workload on the DB instance is memory intensive, and results in an out of memory (OOM) state. This happens even when memory related parameters are not set or are set to default values.
If an Amazon Aurora for MySQL DB instance is in the incompatible-parameters status, then you can only reboot or delete your DB instance. You can't modify the DB instance or the engine version.
Choose the parameter group that you want to reset.
Choose Parameter group actions, and then choose Reset.
Reduce memory for heavy workloads
For memory intensive workloads, reduce the buffer pool size from the default value (75% of memory) to a smaller value. For example, you might use DBInstanceClassMemory*5/8 or DBInstanceClassMemory *1/2. To do this, modify the innodb_buffer_pool_size parameter.
Note: If you modified or reset any static parameters, wait for the modification to be applied. Then, trigger a reboot of the DB instance.