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

ALTER SEQUENCE ends up in optimistic parallel slave binlog out-of-order

    XMLWordPrintable

Details

    Description

      Customer is still facing this issue.

      2023-06-01  0:00:00 9 [ERROR] Slave SQL: Error 'An attempt was made to binlog GTID 1-1-213122284 which would create an out-of-order sequence number with existing GTID 1-1-213122286, and gtid strict mode is enabled' on query. Default database: 'xxxx'. Query: 'Alter Sequence seq_xxxx Restart With 1', Gtid 1-1-213122284, Internal MariaDB error code: 1950
       
      2023-06-01  0:00:00 9 [Warning] Slave: An attempt was made to binlog GTID 1-1-213122284 which would create an out-of-order sequence number with existing GTID 1-1-213122286, and gtid strict mode is enabled Error_code: 1950
       
      2023-06-01  0:00:00 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
      

      Earlier bug: MDEV-31077

      This bug was supposed to be fixed in the intermediate MariaDB ES release 10.6.12-8.
      But seems like the customer is still facing the issue.

      Attachments

        1. Screenshot 2023-09-07 at 5.34.55 PM.png
          Screenshot 2023-09-07 at 5.34.55 PM.png
          33 kB
        2. rpl_parallel_seq_alter.test
          2 kB
        3. my_gdb-5.txt
          2 kB
        4. my_gdb-4.txt
          2 kB
        5. my_gdb-3.txt
          2 kB
        6. my_gdb-2.gdb
          2 kB

        Activity

          People

            Elkin Andrei Elkin
            susmeet.khaire Susmeet Khaire
            Votes:
            2 Vote for this issue
            Watchers:
            7 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.