Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
21.06.17, 22.08.14, 23.02.11, 23.08.7, 24.02.3, 24.08.0
-
None
-
MXS-SPRINT-222, MXS-SPRINT-223
Description
Errors that are caused by max_connections or max_user_connections are treated as authentication failures (which they are) and mark the backend as permanently broken (which it isn't). The backend protocol should not classify these as fatal errors and should instead allow the router to decide if it can continue reconnecting in the hopes that the max_connections limit won't be hit on reconnect.