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

Ping servers to maintain cooperative monitoring locks

    XMLWordPrintable

Details

    • Task
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 25.01.6, 25.10.2
    • 25.01.7, 25.10.3
    • mariadbmon
    • None

    Description

      During cooperative_monitoring, the monitor sets wait_timeout for server connections so that in the case of broken network, the MariaDB Server quickly closes the client connection and releases the lock. The value of wait_timeout is roughly monitor_interval + 2 * backend_timeout. The assumption is that a normal monitor tick cannot take longer than wait_timeout, even if server is slow to respond to monitor queries.

      This assumption may not hold in all cases: A monitor update of one server contains several steps, if every step is slow (up to the configured timeout), the update as a whole can take longer than wait_timeout. If one server finishes its update quickly but another is slow, the fast server may hit wait_timeout before the next tick begins.

      To protect against this, once the monitor has a completed a tick on a server, the monitor should keep pinging that server until all servers have completed their ticks.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              esa.korhonen Esa Korhonen
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.