What should the database specialist do to control the idle connections in the database?
Modify the MaxConnectionsPercent parameter through the RDS Proxy console.
Use CALL mysql.rds_kill(thread-id) for the IDLE threads that are returned from the SHOW FULL PROCESSLIST command.
Modify the MaxIdleConnectionsPercent parameter for the RDS proxy.
Modify the max_connections configuration setting for the DB instance. Modify the ConnectionBorrowTimeout parameter for the RDS proxy.
Explanations:
TheMaxConnectionsPercentparameter in RDS Proxy controls the maximum number of connections that can be established to the database, not idle connections specifically. It does not directly affect the management of idle connections.
UsingCALL mysql.rds_kill(thread-id)is a manual method to terminate idle threads, but this is not an automated or optimal way to manage idle connections. RDS Proxy handles connection pooling and idle connection management.
TheMaxIdleConnectionsPercentparameter in RDS Proxy controls the maximum percentage of idle connections that can be maintained in the proxy’s connection pool. This directly manages idle connections, making this the correct approach.
Modifying themax_connectionssetting on the DB instance affects the total number of connections allowed, not specifically idle connections. TheConnectionBorrowTimeoutparameter affects the time RDS Proxy waits for an available connection but does not directly control idle connections.
I gauge that the answer is:
Modify the MaxIdleConnectionsPercent parameter for the RDS proxy.