AWS-RDS does not provide any user with SUPER privilege. As a result, 'too many connections' are made, even the dba is locked out. Nobody can login and kill any sleeping connection. Apart from taking pre-emptive actions to avoid 'too many connections' like creating an event scheduler to kill sleeping connections, how to deal with the error?

  • What are the client(s)? Apache? Tomcat? ...? – Rick James May 8 '19 at 17:00
  • Have you considered simply increasing the number of allowed connections? – Michael - sqlbot May 9 '19 at 0:19
  • Fix the slow queries, like this non-AWS answer. A server can support 10 connection x 100ms queries in a second, however if the query time is reduced to 5ms, 200 connections can be supported (roughly and slightly hand-wavy). – danblack May 9 '19 at 4:53
  • @RickJames : Tomcat. – Subrata Das May 9 '19 at 6:27
  • @Michael-sqlbot : Yes, we have already increased the number of allowed connections. I am looking for a way to login to RDS when the server is giving 'too many connections' error – Subrata Das May 9 '19 at 6:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.