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

Allow pinloki failover to be performed by the monitor

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.5.5
    • Monitor, pinloki
    • None
    • MXS-SPRINT-116, MXS-SPRINT-117

    Description

      Currently pinloki will switch to a new primary if the current one goes down. This is not correct in the case where the failover is initiated via maxscale (i.e. the old primary does not go down, but becomes a replica).

      Attachments

        Activity

          People

            nantti Niclas Antti
            nantti Niclas Antti
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Time Spent - 5d 3h Remaining Estimate - 3.25d
                3.25d
                Logged:
                Time Spent - 5d 3h Remaining Estimate - 3.25d
                5d 3h

                Git Integration

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