By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

MySQL RDS 'max_connections_per_hour' error, what are my options. This is not the 'max_connections' parameters, but per hour.

0

I'm getting the following error for a DB I have. (db.t2.micro)

“1226 (42000): User ‘?????????’ has exceeded the ‘max_connections_per_hour’ resource (current value: 85)”

Note that this is not the typical 'max_connections' parameter.

I do not see the parameter under my.sql.user (as if it doesn't exist), but I am getting the error nonetheless.

Most of the solutions that I read about include upgrading the instance, which I am willing to do but for my current application it would be overkill. Most of my open and close connections are simple api request.

85 connections in an hour doesn't seem like much, there has to be another solution.

Topics
Migration & ModernizationAnalyticsDatabase
Tags
Amazon Relational Database ServiceDatabase
Language
English
rePost-User-2370401
asked 2 years ago616 views
1 Answer
0

MAX_CONNECTIONS_PER_HOUR is a MySQL per-user parameter. To remove this, you can use:

ALTER USER user@host MAX_CONNECTIONS_PER_HOUR 0;
profile pictureAWS
EXPERT
Chris_G
answered 2 years ago
  • rePost-User-2370401
    2 years ago

    This fixed it. It's weird, the USER table does not have this parameter visible, and the mysql feedback from running the query is '0 rows affected', but it did work.

  • Chris_G EXPERT
    2 years ago

    You can check this with SELECT User, max_connections, max_user_connections FROM mysql.user;. The 0 rows affected is normal, this happens with any alters to users. Can you mark this answer correct if it answered your question?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content