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

Parameter to prevent promotion of a replica which has had Error 1236

    XMLWordPrintable

    Details

    • Sprint:
      MXS-SPRINT-170, MXS-SPRINT-171

      Description

      Requesting a way to prevent MariaDB Monitor from promoting a replica which has had an Error 1236 - ER_MASTER_FATAL_ERROR_READING_BINLOG - or similar fatal replication error.

      Suggesting a parameter for MariaDB Monitor, something like auto_failover_strict_mode.

      In the referenced support case, customer had a primary with two replicas. One replica was out of sync due to a 1236 error. In a subsequent failover situation, the out of sync replica was promoted to primary, causing the other nodes to be out of sync later.

      A parameter such as auto_failover_strict_mode would have prevented MariaDB Monitor from promoting the out of sync replica, even if that would result in a longer outage.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            bengrieser Ben Grieser
            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.