Why is my Amazon Aurora DB instance in an incompatible parameter status?

Last updated: 2020-12-14

I have an Amazon Aurora DB instance that is in an "incompatible-parameters" status. Why is my DB instance in an incompatible-parameter status, and how can I resolve this issue?

Short description

The incompatible-parameters status occurs when one of the parameters in the associated parameter group has a value that isn't compatible with either the current engine version you are using, or the current DB instance class and size.

If an Amazon Aurora for MySQL DB instance is in the incompatible-parameters status, you can only reboot or delete your DB instance. You can't modify the DB instance or the engine version.

A DB instance might be in the incompatible-parameters state for the following reasons:

  • The sum of memory used by parameters in both the cluster and the instance parameter groups is higher than the available memory on the DB 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 set to default values.

Resolution

Note: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version.

To identify the root cause of the issue, first copy the incompatible parameter group. Then, compare the differences between the custom parameter values and the default values. For more information, see Working with DB parameter groups.

After you identify the issue, resolve an incompatible-parameters status using one of the following methods.

Reset incompatible parameter values

Follow these steps to reset only the incompatible parameter values:

  1. Open the Amazon Relational Database Service (Amazon RDS) console, and from the Navigation panel, choose Parameter groups.
  2. Choose the incompatible parameter group, and then choose Edit parameters.
  3. Enter valid (lower memory usage) parameter values, and then choose Save changes.
  4. Reboot the DB instance to apply the new settings.

Reset all the parameters in the parameter group to their default values

Follow these steps using the Amazon RDS Console to reset all parameters in the parameter group to default values:

  1. Open the Amazon RDS Console, and from the Navigation panel, choose Parameter groups.
  2. Choose the incompatible parameter group, and then choose Reset.

Note: Using the Amazon RDS Console to complete this step allows you to change parameters to any allowed or related values. Completing this step using the AWS CLI allows you to reset the target parameters only to their default values.

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, such as DBInstanceClassMemory*5/8 or DBInstanceClassMemory *1/2. You can do this by modifying the innodb_buffer_pool_size parameter.

Note: If you modified or reset any static parameters, wait for the modification to be applied, and then trigger a reboot of the DB instance.


Did this article help?


Do you need billing or technical support?