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

Allow to make extra_port the default, not the fallback, for monitors

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.4.11, 2.5.2
    • 6.0.0
    • Monitor
    • None
    • MXS-SPRINT-116

    Description

      Right now the extra_port defined for a server will only be used when a connect attempt on the regular port fails

      "This allows MaxScale to connect even when max_connections has been reached on the backend server. If this parameter is defined and a connection to the normal port fails, the alternative port is used."

      As even when successfully connected to the regular port monitoring queries on that connection can stall while waiting in the pool-of-threads execution queue it would IMHO make more sense to have the monitor(s) use the extra port by default, to ensure that monitoring queries and switchover/failover actions are handled with priority and don't have to wait in the thread pool execution queue if the thread pool is fully loaded with query execution threads already.

      Monitoring queries will still suffer from CPU overload if pool-of-threads was not properly configured to prevent this, but at least they won't additionally suffer from having to wait in the thread pool queue in such cases, too.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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