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

Shows replication time difference in master_last_event_time after setting MASTER_DELAY > 0 in chain replication

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 11.6.0
    • 11.6.0
    • Replication
    • None

    Description

      Found a small difference in Master_last_event_time in replica2 when setting up chain replication. The issue found only when setting MASTER_DELAY > 0 on replica1

      Test case

      MariaDB [test]> create or replace table t1 select seq from seq_1_to_1000;select now();
      Query OK, 1000 rows affected (0.086 sec)
      Records: 1000  Duplicates: 0  Warnings: 0
       
      +---------------------+
      | now()               |
      +---------------------+
      | 2024-06-07 10:16:25 |
      +---------------------+
      1 row in set (0.000 sec)
       
      MariaDB [test]> 
      

      replica status from server replica1. Master delay configured to 5 sec on replica1 SQL_Delay: 5

                       Parallel_Mode: aggressive
                           SQL_Delay: 5
                 SQL_Remaining_Delay: NULL
             Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
                    Slave_DDL_Groups: 8
      Slave_Non_Transactional_Groups: 2
          Slave_Transactional_Groups: 1
                Retried_transactions: 0
                  Max_relay_log_size: 1073741824
                Executed_log_entries: 1327
           Slave_received_heartbeats: 67
              Slave_heartbeat_period: 30.000
                      Gtid_Slave_Pos: 11-100-11
              Master_last_event_time: 2024-06-07 10:16:25
               Slave_last_event_time: 2024-06-07 10:16:25
              Master_Slave_time_diff: 0
      1 row in set (0.000 sec)
       
      MariaDB [test]> 
      

      replica status from server replica2, please check Master_last_event_time difference

                           SQL_Delay: 0
                 SQL_Remaining_Delay: NULL
             Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
                    Slave_DDL_Groups: 1
      Slave_Non_Transactional_Groups: 9
          Slave_Transactional_Groups: 1
                Retried_transactions: 0
                  Max_relay_log_size: 1073741824
                Executed_log_entries: 1308
           Slave_received_heartbeats: 91
              Slave_heartbeat_period: 30.000
                      Gtid_Slave_Pos: 11-100-11
              Master_last_event_time: 2024-06-07 10:16:30
               Slave_last_event_time: 2024-06-07 10:16:25
              Master_Slave_time_diff: 5
      1 row in set (0.000 sec)
       
      MariaDB [test]> 
      

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              ramesh Ramesh Sivaraman
              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.