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

Automatic discovery of Primary/Replica cluster

    XMLWordPrintable

Details

    • New Feature
    • Status: In Progress (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • 25.08
    • mariadbmon
    • None
    • MXS-SPRINT-220, MXS-SPRINT-221, MXS-SPRINT-222

    Description

      The use-case of this feature should be clarified. Two possibilities come to mind:
      1. A replication cluster (even if just one server) is already running, but servers are not configured in MaxScale. DBA wants an easy way to configure all servers at once so they are in MaxScale and monitored.
      2. DBA wants to add or remove servers from an already monitored cluster.

      Original description:
      Currently the servers to be monitored by MariaDB Monitor must be explicitly listed. In the case of a simple primary/replica cluster that is quite unnecessary as all needed information can be obtained by probing the servers. Basically the only thing the monitor needs to know is the address of one server; after that it can find the rest. If a new server is added to the cluster, the monitor could notice that and act appropriately.

      If a service then is configured with the cluster argument pointing to the monitor, it would be very simple to get the system up and running. All that needs to be provided to the monitor is the address of one server and the monitor would figure out the rest.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            johan.wikman Johan Wikman
            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.