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

Track master timestamp in case rolling back to serial replication

Details

    Description

      I tried to switch on parallel replication from Amazon Aurora to MariaDB.

      [my.cnf]
      slave-parallel-threads = 4
      slave-parallel-mode = optimistic

      'set global .slave_parallel_mode=optimistic;'
      As I understand now it doesn't have sense because it's rolling back to serial replication. But it introduces a silent problem with Seconds_behind_master. This value always = 0.

      So, probably, would be good to keep this metric even in this unnatural but working mode.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34778 Inconsistent Seconds_Behind_Master after slave stop+start (rpl.rpl_old_master sporadic failure)

          • Major - Major loss of function.
          • Open

          Activity

            Transition Time In Source Status Execution Times
            Andrei Elkin made transition -
            Open Closed
            		342d 10h 2m 1
            Marko Mäkelä made transition -
            Closed Stalled
            		15h 58m 1
            Andrei Elkin made transition -
            Stalled Closed
            		8h 1m 1

            People

              Elkin Andrei Elkin
              svoj Sergey Vojtovich
              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.