Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-27378

Could not find GTID state requested by slave in any binlog files

    XMLWordPrintable

    Details

      Description

      When I switchover but on maxscale but when master change to slave is failed and I got this message on mysql_error.log

      2021-12-28 12:09:59 12 [Note] Error reading relay log event: slave SQL thread was killed
      2021-12-28 12:09:59 12 [Note] Slave SQL thread exiting, replication stopped in log 'mysql-bin.000970' at position 401; GTID position '0-208-83304652,1-28-150850264'
      2021-12-28 12:09:59 11 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000970', position 401; GTID position 1-28-150850264,0-208-83304652
      2021-12-28 12:09:59 8755 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='172.17.70.154', master_port='13313', master_log_file='mysql-bin.000970', master_log_pos='401'. New state master_host='172.17.70.208', master_port='13313', master_log_file='', master_log_pos='4'.
      2021-12-28 12:09:59 8755 [Note] Previous Using_Gtid=Current_Pos. New Using_Gtid=Current_Pos
      2021-12-28 12:09:59 9108 [Note] Slave I/O thread: Start semi-sync replication to master 'maxscale@172.17.70.208:13313' in log '' at position 4
      2021-12-28 12:09:59 9109 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 4, relay log './i8-drc28-25-relay-bin.000001' position: 4; GTID position '0-208-83304652,1-28-150850264'
      2021-12-28 12:09:59 9108 [Note] Slave I/O thread: connected to master 'maxscale@172.17.70.208:13313',replication starts at GTID position '1-28-150850264,0-208-83304652'
      2021-12-28 12:10:00 9108 [ERROR] Error reading packet from server: Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged. (server_errno=1236)
      2021-12-28 12:10:00 9108 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged.', Internal MariaDB error code: 1236
      2021-12-28 12:10:00 9108 [Note] Slave I/O thread exiting, read up to log 'FIRST', position 4; GTID position 1-28-150850264,0-208-83304652
      
      

      this is config on mariadb

      [server]
      log_warnings=1
      server_id=208
      gtid_ignore_duplicates=ON
      gtid_strict_mode=1
      rpl_semi_sync_master_enabled=ON
      rpl_semi_sync_slave_enabled=ON
      rpl_semi_sync_master_wait_point=AFTER_SYNC
      slave-skip-errors=1062,1032
      
      

      [server]
      log_warnings=1
      server_id=28
      gtid-domain-id=1
      gtid_ignore_duplicates=ON
      gtid_strict_mode=1
      rpl_semi_sync_master_enabled=ON
      rpl_semi_sync_slave_enabled=ON
      rpl_semi_sync_master_wait_point=AFTER_SYNC
      slave-skip-errors=1062,1032
      

      that is issue from configuration or other issue

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            febridev febriyant
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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