![]() Note: Aurora MySQL and Amazon Relational Database Service (Amazon RDS) MySQL DB instances have different amounts of memory overhead. Dynamic in nature (no reboot is required to change this parameter value).įor more information on the default value of max_connections for each DB instance class available to Aurora MySQL, see Maximum connections to an Aurora MySQL DB instance.Allowed value is an integer in the range of 1-16000.However, instance-level parameter setting takes effect. Can be set on both the DB cluster and DB instance parameter group.To do this, check the parameter group attached to your DB instance or by run the following query: select max_connections parameter has the following specifications: See the following example: max_connections = GREATEST()Ĭheck the current value of the max_connections parameter for your DB instance. Note: The maximum number of connections allowed to an Aurora MySQL DB instance is determined by the max_connections parameter in the instance-level parameter group for the DB instance. For more information, see Working with DB parameter groups. Changing the parameter group causes an outage. Increasing the max_connections parameter doesn't cause an outage, but if your DB instance is using a default parameter group, then change the parameter group to a custom parameter group. Set a larger value for the max_connections parameter using a custom instance-level parameter group.Note: Scaling the DB instance class causes an outage. Scale the instance up to a DB instance class with more memory.Increase the maximum number of connections to your DB instance using the following methods: Terminate user sessions or queries currently running on your DB instance by running the rds_kill and rds_kill_query commands: CALL mysql.rds_kill(thread-ID) ĬALL mysql.rds_kill_query(thread-ID) Increase the maximum connections to your DB instance Terminate existing connections on your DB instance Increase the maximum number of connections to your DB instance.For example, start by terminating connections in sleep state. Review existing connections and, if possible, terminate them to release connection pressure.Resolve the max connection error using one of the following methods: Enable logging on Aurora MySQL DB instanceĮnable logging on your Aurora MySQL DB instance by enabling general_log, slow_query_log or advanced auditing log parameters. Note: The SHOW FULL PROCESSLIST and INFORMATION_SCHEMA.PROCESSLIST statements can negatively affect performance because they require a mutex. ![]() For more information, see the MySQL documentation for Privileges provided by MySQL. Otherwise, SHOW PROCESSLIST shows only the threads associated with the MySQL account that you're using. Note: You must grant your user account the administration privilege for the MySQL PROCESS server to see all the threads running on a MySQL DB instance. ![]() You can also run the following query to get the same result set: SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST Log in to your DB instance, and then run the following query: SHOW FULL PROCESSLIST\G The SHOW FULL PROCESSLIST command shows which threads are currently running on your DB instance. Show threads currently running on Aurora MySQL DB instance Then, enable logging on your DB instance.
0 Comments
Leave a Reply. |