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

Automatic rejoin failed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: 6.1.0
    • Fix Version/s: N/A
    • Component/s: failover
    • Labels:
      None

      Description

      [mariadbmon] Automatic rejoin was not attempted on server 'server1' even though it is a valid candidate. Will keep retrying with this message suppressed for all servers. Errors:
      gtid_current_pos of 'server1' (0-1-19) is incompatible with gtid_binlog_pos of 'server2' (0-2-6).

      Master DB (10.6) replication config:
      server-id=1
      gtid_strict_mode=1
      log-slave-updates=ON
      log-bin = /var/lib/mysql/bin-mariadb.log
      expire-logs-days=8
      sync_binlog = 1
      slave_compressed_protocol
      transaction-isolation = READ-COMMITTED
      binlog_format = row

      Maxscale (6-1-1-GA) config:
      monitor_interval=100
      auto_failover=true
      auto_rejoin=true
      enforce_read_only_slaves=1
      backend_connect_timeout=2
      backend_read_timeout=2
      backend_write_timeout=2
      master_failure_timeout=2
      verify_master_failure=true
      failcount=2
      switchover_timeout=20
      failover_timeout=20

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            csulit Christian Angelo Sulit
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration