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

Master Recovery With Delayed Slaves

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.3.6
    • Fix Version/s: N/A
    • Component/s: failover
    • Labels:
      None

      Description

      In a situation where a master has two slaves on delayed replication and the master goes down, Maxscale cannot promote a slave due to replication lag until the delay has expired.

      However, if the original master becomes available again before the slave delay expires, the master should automatically resume it's previous role.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            toddstoffel Todd Stoffel
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.