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

Parallel replication causes failed assert while restarting

    XMLWordPrintable

Details

    Description

      Test Case

      --source include/master-slave.inc
       
      --connection slave
      --source include/stop_slave.inc
      --let $old_parallel= `select @@GLOBAL.slave_parallel_threads`
      SET GLOBAL slave_parallel_threads=8;
      --source include/start_slave.inc
       
      --let $rpl_server_no= 2
      --source include/rpl_restart_server.inc
       
      --connection slave
      --eval SET GLOBAL slave_parallel_threads= $old_parallel
      --source include/start_slave.inc
      --source include/rpl_end.inc
      
      

      It does not fail in 10.5

      Failure

      rpl.tmp 'mix'                            [ fail ]  Found warnings/errors in server log file!
              Test ended at 2021-04-05 09:19:24
      line
      mysqld: sql/sql_list.h:642: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
      mysqld: sql/sql_list.h:642: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
      mysqld: sql/sql_list.h:642: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
      mysqld: sql/sql_list.h:642: void ilink::assert_linked(): Assertion `prev != 0 && next != 0' failed.
      Attempting backtrace. You can use the following information to find out
      ^ Found warnings in /home/sachin/10.3/mysql-test/var/log/mysqld.2.err
      ok
      
      

      Attachments

        Activity

          People

            sachin.setiya.007 Sachin Setiya (Inactive)
            sachin.setiya.007 Sachin Setiya (Inactive)
            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.