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

Not all state transitions are written to the log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.1.4
    • Fix Version/s: 6.2.3
    • Component/s: Monitor
    • Labels:
      None

      Description

      Some monitor state transitions are not written to the log when log_info is enabled.

      E.g. a binlog routers transition from Binlog Relay, Running to Down is logged when it is on another maxscale instance and that one is being shut down, but when doing a STOP SLAVE on a binlog router causing a transition from Binlog Relay, Running to just Running this is not directly seen in the maxscale log at all.

      What is seen though is actual slaves replicating form that binlog router loosing their master and switching from Slave; Running to just Running due to this.

      Seeing that the binlog router changed state at around the same time would make understanding the state changes of the actual replicas more understandable when analyzing logs.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            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.