Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-5382

Errors due to max_connections being exceeded are always fatal errors

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 21.06.17, 22.08.14, 23.02.11, 23.08.7, 24.02.3, 24.08.0
    • None
    • Protocol, readwritesplit
    • None
    • MXS-SPRINT-222

    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.

      Attachments

        Activity

          People

            markus makela markus makela
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.