For the most recent update on ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), refer to the AWS Health Dashboard. For information on AWS Service migration, see How do I migrate my services to another region?
Why won't the updated parameter values take effect after I change the parameter values in an Amazon RDS parameter group?
I modified the values of parameters in the parameter group for my Amazon Relational Database Service (Amazon RDS) DB instance. However, the updated values aren't taking effect.
Short description
Amazon RDS DB instances are either static or dynamic. When you update the value of a static parameter, the changes don't take effect immediately. You must manually reboot the associated DB instance for the parameter group changes to take effect. When you update a dynamic parameter, Amazon RDS applies the parameter changes to your DB instance immediately. In this case, you don't have to reboot the DB instance.
Resolution
Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.
To check if the parameter that you're modifying is static or dynamic, complete the following steps:
- Open the Aurora and RDS console
- In the navigation pane, choose Parameter groups.
- Select the parameter group that you want to modify.
- For the parameter that you want to modify, check the column Apply type.
Note: The Apply type column displays for both dynamic and static parameters.
Or, run the describe-db-parameters AWS CLI command:
aws rds describe-db-parameters --db-parameter-group-name test_parameter_group --query "Parameters[*].[ParameterName,ApplyType]"
Note: Replace test_parameter_group with the name of your custom parameter group.
The preceding command returns the list of parameters in a parameter group along with Apply type.
To check the status of the parameter group, complete the following steps:
- Open the Aurora and RDS console.
- In the navigation pane, choose Databases, and then select the DB instance.
- Choose the Configuration tab.
- Check the parameter group status.
If the DB parameter group has a status of pending-reboot, then the parameter that you're modifying is static.
Or, run the describe-db-instances AWS CLI command to verify the status of the parameter group:
aws rds describe-db-instances --db-instance-identifier instance_identifier --query "DBInstances[*]".[DBInstanceIdentifier,DBParameterGroups]
Note: Replace instance_identifier with the name of your RDS instance.
If the parameter that you're modifying is static, then reboot the instance. When you reboot a DB instance, there's a momentary outage. During this outage, the DB instance status is set to rebooting. After the instance reboots successfully, changes to the static parameters take effect on the associated RDS instance. The status of the parameter group changes from pending-reboot to in-sync.
Note: When you associate a new DB parameter group with a DB instance, the Aurora and RDS console shows the DB parameter group with a pending-reboot status. To apply modified static and dynamic parameters, you must reboot the instance. However, if you modify dynamic parameters after you associate the DB parameter group, then Amazon RDS applies the changes immediately without a reboot.
Related information
How do I modify the values of an Amazon RDS DB parameter group?
- Language
- English
Hey, i have changed the dynamic parameter value(work_mem, max_parallel_workers_per_gather) but still when running command SHOW ALL; it's showing the old value only. why is it so? And also when I am rebooting the instance after changing the parameters it's taking more than an hour to come back in available state. why taking so much time?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Relevant content
- asked 4 years ago
