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

Bad `create monitor` command leaves a ghost monitor

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.4.0
    • Fix Version/s: 6.4.1
    • Component/s: REST-API
    • Labels:
      None

      Description

      When the creation of a monitor fails at runtime, if another monitor already monitors one of the servers given in the initial servers relationship, the "unclaimed" servers that aren't monitored by anything are permanenty linked with the monitor being created. This causes further attempts to use them to fail with an error that states they are already monitored by another monitor.

      The following commands will reproduce the problem:

      maxctrl create server server1 127.0.0.1 3000
      maxctrl create monitor MariaDB-Monitor mariadbmon user=maxuser password=maxpwd --servers server1 server1
      

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.