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

MariaDB 10.5.4 and 10.5.6 replica keeps crashing when the a 10.2.x master run a `ALTER TABLE CHARACTER utf8mb4`

    XMLWordPrintable

Details

    Description

       
      2020-10-15 19:41:10 0 [Note] InnoDB: Using Linux native AIO
      2020-10-15 19:41:10 0 [Note] InnoDB: Uses event mutexes
      2020-10-15 19:41:10 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-10-15 19:41:10 0 [Note] InnoDB: Number of pools: 1
      2020-10-15 19:41:10 0 [Note] InnoDB: Using SSE4.2 cr
      2020-10-15 19:41:10 0 [Note] InnoDB: Trx id counter is 21784530053
      2020-10-15 19:41:10 0 [Note] InnoDB: Last binlog file '/data1/mysql/binlog/mysql-bin.036747', position 174666394
      2020-10-15 19:41:10 0 [Note] InnoDB: 128 rollback segments are active.
      2020-10-15 19:41:10 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
      2020-10-15 19:41:10 0x7fb307b2f700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/data/data0type.cc line 67
      InnoDB: Failing assertion: !(prefix_len % mbmaxlen)
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      201015 19:41:10 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 10.5.6-MariaDB-log
      key_buffer_size=33554432
      read_buffer_size=16777216
      max_used_connections=0
      max_threads=2002
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 65684329 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x49000
      2020-10-15 19:41:10 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-10-15 19:41:10 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2020-10-15 19:41:10 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-10-15 19:41:10 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2020-10-15 19:41:10 0 [Note] InnoDB: 10.5.6 started; log sequence number 14517572805836; transaction id 21784530055
      2020-10-15 19:41:10 0 [Note] InnoDB: Loading buffer pool(s) from /data1/mysql/data/ib_buffer_pool
      2020-10-15 19:41:10 0 [Note] Plugin 'FEEDBACK' is disabled.
      2020-10-15 19:41:10 0 [Note] Recovering after a crash using /data1/mysql/binlog/mysql-bin
      2020-10-15 19:41:10 0 [Note] Starting crash recovery...
      2020-10-15 19:41:10 0 [Note] Crash recovery finished.
      2020-10-15 19:41:10 0 [Note] Server socket created on IP: '10.0.30.1'.
      2020-10-15 19:41:10 0 [Note] Reading of all Master_info entries succeeded
      2020-10-15 19:41:10 0 [Note] Added new Master_info '' to hash table
      2020-10-15 19:41:10 0 [Note] /data1/app/mariadb/bin/mariadbd: ready for connections.
      Version: '10.5.6-MariaDB-log'  socket: '/data1/mysql/run/mysqld.sock'  port: 3306  MariaDB Server
      /data1/app/mariadb/bin/mariadbd(my_print_stacktrace+0x2e)[0x55b9a167a58e]
      /data1/app/mariadb/bin/mariadbd(handle_fatal_sig
      ??:0(gsignal)[0x7fb5323267bb]
      ??:0(abort)[0x7fb532311535]
      /data1/app/mariadb/bin/mariadbd(+0x6c4d43)[0x55b9a0d32d43]
      /data1/app/mariadb/bin/mariadbd(+0xebf0cc)[0x55b9a152d0cc]
      :0(ut_dbg_assertion_failed(char const*, char const*, unsigned int))[0x55b9a1452c61]
      data/data0type.cc:67(dtype_get_at_most_n_mbchars(unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, char const*))[0x55b9a15f157c]
      include/data0data.ic:54(dfield_set_len)[0x55b9a14604f8]
      row/row0uins.cc:482(row_undo_ins_remove_sec_rec)[0x55b9a1406bd7]
      row/row0undo.cc:442(row_undo)[0x55b9a149e476]
      que/que0que.cc:945(que_thr_step)[0x55b9a14a0a1c]
      trx/trx0roll.cc:631(trx_rollback_active(trx_t*))[0x55b9a14a0da0]
      ??:0(start_thread)[0x7fb53280efa3]
      ??:0(clone)[0x7fb5323e84cf]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /data1/mysql/data
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited            bytes
      Max data size             unlimited            unlimited            bytes
      Max stack size            8388608              unlimited            bytes
      Max core file size        0                    unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             257066               257066               processes
      Max open files            1024000              1024000              files
      Max locked memory         67108864             67108864             bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       257066               257066               signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: core
       
      2020-10-15 19:41:11 0 [Note] InnoDB: Using Linux native AIO
      2020-10-15 19:41:11 0 [Note] InnoDB: Uses event mutexes
      2020-10-15 19:41:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-10-15 19:41:11 0 [Note] InnoDB: Number of pools: 1
      2020-10-15 19:41:11 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
      2020-10-15 19:41:11 0 [Note] InnoDB: Initializing buffer pool, total size = 8589934592, chunk size = 134217728
      2020-10-15 19:41:11 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-10-15 19:41:11 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2020-10-15 19:41:11 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14517572805942
      2020-10-15 19:41:11 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1 row operations to undo
      2020-10-15 19:41:11 0 [Note] InnoDB: Trx id counter is 21784530053
      2020-10-15 19:41:11 0 [Note] InnoDB: Last binlog file '/data1/mysql/binlog/mysql-bin.036747', position 174666394
      2020-10-15 19:41:11 0 [Note] InnoDB: 128 rollback segments are active.
      2020-10-15 19:41:11 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
      2020-10-15 19:41:11 0x7ff7bd775700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/data/data0type.cc line 67
      InnoDB: Failing assertion: !(prefix_len % mbmaxlen)
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes
      something is definitely wrong and this may fail.
       
      Server version: 10.5.6-MariaDB-log
      key_buffer_size=33554432
      read_buffer_size=16777216
      max_used_connections=0
      max_threads=2002
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 65684329 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x0 thread_stack 0x49000
      2020-10-15 19:41:11 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-10-15 19:41:11 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2020-10-15 19:41:11 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-10-15 19:41:11 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2020-10-15 19:41:11 0 [Note] InnoDB: 10.5.6 started; log sequence number 14517572806048; transaction id 21784530055
      2020-10-15 19:41:11 0 [Note] InnoDB: Loading buffer pool(s) from /data1/mysql/data/ib_buffer_pool
      2020-10-15 19:41:11 0 [Note] Plugin 'FEEDBACK' is disabled.
      2020-10-15 19:41:11 0 [Note] Recovering after a crash using /data1/mysql/binlog/mysql-bin
      2020-10-15 19:41:11 0 [Note] Starting crash recovery...
      2020-10-15 19:41:11 0 [Note] Crash recovery finished.
      2020-10-15 19:41:11 0 [Note] Server socket created on IP: '10.0.30.1'.
      2020-10-15 19:41:11 0 [Note] Reading of all Master_info entries succeeded
      2020-10-15 19:41:11 0 [Note] Added new Master_info '' to hash table
      2020-10-15 19:41:11 0 [Note] /data1/app/mariadb/bin/mariadbd: ready for connections.
      Version: '10.5.6-MariaDB-log'  socket: '/data1/mysql/run/mysqld.sock'  port: 3306  MariaDB Server
      /data1/app/mariadb/bin/mariadbd(my_print_stacktrace+0x2e)[0x563dd3dbf58e]
      /data1/app/mariadb/bin/mariadbd(handle_fatal_signal+0x307)[0x563dd3798897]
      ??:0(__restore_rt)[0x7ff9e83ab730]
      ??:0(gsignal)[0x7ff9e7eb87bb]
      ??:0(abort)[0x7ff9e7ea3535]
      /data1/app/mariadb/bin/mariadbd(+0x6c4d43)[0x563dd3477d43]
      /data1/app/mariadb/bin/mariadbd(+0xebf0cc)[0x563dd3c720cc]
      :0(ut_dbg_assertion_failed(char const*, char const*, unsigned int))[0x563dd3b97c61]
      data/data0type.cc:67(dtype_get_at_most_n_mbchars(unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, char const*))[0x563dd3d3657c]
      include/data0data.ic:54(dfield_set_len)[0x563dd3ba54f8]
      row/row0uins.cc:482(row_undo_ins_remove_sec_rec)[0x563dd3b4bbd7]
      row/row0undo.cc:442(row_undo)[0x563dd3be3476]
      que/que0que.cc:945(que_thr_step)[0x563dd3be5a1c]
      trx/trx0roll.cc:631(trx_rollback_active(trx_t*))[0x563dd3be5da0]
      ??:0(start_thread)[0x7ff9e83a0fa3]
      ??:0(clone)[0x7ff9e7f7a4cf]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /data1/mysql/data
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited
      Max open files            1024000              1024000              files
      Max locked memory         67108864             67108864             bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       257066               257066               signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: core
       
      2020-10-15 19:41:12 0 [Note] InnoDB: Using Linux native AIO
      2020-10-15 19:41:12 0 [Note] InnoDB: Uses event mutexes
      2020-10-15 19:41:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-10-15 19:41:12 0 [Note] InnoDB: Number of pools: 1
      2020-10-15 19:41:12 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
      2020-10-15 19:41:12 0 [Note] InnoDB: Initializing buffer pool, total size = 8589934592, chunk size = 134217728
      2020-10-15 19:41:12 0 [Note] InnoDB: Completed initialization of buffer pool
      2020-10-15 19:41:12 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
      2020-10-15 19:41:12 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=14517572805942
      2020-10-15 19:41:12 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1 row operations to undo
      2020-10-15 19:41:12 0 [Note] InnoDB: Trx id counter is 21784530053
      2020-10-15 19:41:12 0 [Note] InnoDB: Last binlog file '/data1/mysql/binlog/mysql-bin.036747', position 174666394
      2020-10-15 19:41:13 0 [Note] InnoDB: 128 rollback segments are active.
      2020-10-15 19:41:13 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
      2020-10-15 19:41:13 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-10-15 19:41:13 0 [Note] InnoDB: Creating shared tablespace for temporary tables
      2020-10-15 19:41:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
      2020-10-15 19:41:13 0x7fb014f74700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/storage/innobase/data/data0type.cc line 67
      InnoDB: Failing assertion: !(prefix_len % mbmaxlen)
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      201015 19:41:13 [ERROR] mysqld got signal 6 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed,
      something is definitely wrong and this may fail.
       
      Server version: 10.5.6-MariaDB-log
      key_buffer_size=33554432
      read_buffer_size=16777216
      max_used_connections=0
      max_threads=2002
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 65684329 K
      2020-10-15 19:41:13 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
      2020-10-15 19:41:13 0 [Note] InnoDB: 10.5.6 started; log sequence number 14517572806170; transaction id 21784530055
      2020-10-15 19:41:13 0 [Note] InnoDB: Loading buffer pool(s) from /data1/mysql/data/ib_buffer_pool
      2020-10-15 19:41:13 0 [Note] Plugin 'FEEDBACK' is disabled.
      2020-10-15 19:41:13 0 [Note] Recovering after a crash using /data1/mysql/binlog/mysql-bin
      2020-10-15 19:41:13 0 [Note] Starting crash recovery...
      2020-10-15 19:41:13 0 [Note] Crash recovery finished.
      2020-10-15 19:41:13 0 [Note] Server socket created on IP: '10.0.30.1'.
      2020-10-15 19:41:13 0 [Note] Reading of all Master_info entries succeeded
      2020-10-15 19:41:13 0 [Note] Added new Master_info '' to hash table
      2020-10-15 19:41:13 0 [Note] /data1/app/mariadb/bin/mariadbd: ready for connections.
      Version: '10.5.6-MariaDB-log'  socket: '/data1/mysql/run/mysqld.sock'  port: 3306  MariaDB Server
      /data1/app/mariadb/bin/mariadbd(my_print_stacktrace+0x2e)[0x55c74151c58e]
      /data1/app/mariadb/bin/mariadbd(handle_fatal_signal+0x307)[0x55c740ef5897]
      ??:0(__restore_rt)[0x7fb23f8e5730]
      ??:0(gsignal)[0x7fb23f3f27bb]
      ??:0(abort)[0x7fb23f3dd535]
      /data1/app/mariadb/bin/mariadbd(+0x6c4d43)[0x55c740bd4d43]
      /data1/app/mariadb/bin/mariadbd(+0xebf0cc)[0x55c7413cf0cc]
      :0(ut_dbg_assertion_failed(char const*, char const*, unsigned int))[0x55c7412f4c61]
      data/data0type.cc:67(dtype_get_at_most_n_mbchars(unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, char const*))[0x55c74149357c]
      include/data0data.ic:54(dfield_set_len)[0x55c7413024f8]
      row/row0uins.cc:482(row_undo_ins_remove_sec_rec)[0x55c7412a8bd7]
      row/row0undo.cc:442(row_undo)[0x55c741340476]
      que/que0que.cc:945(que_thr_step)[0x55c741342a1c]
      trx/trx0roll.cc:631(trx_rollback_active(trx_t*))[0x55c741342da0]
      ??:0(start_thread)[0x7fb23f8dafa3]
      ??:0(clone)[0x7fb23f4b44cf]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /data1/mysql/data
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units
      Max cpu time              unlimited            unlimited            seconds
      Max file size             unlimited            unlimited            bytes
      Max data size             unlimited            unlimited            bytes
      Max stack size            8388608              unlimited            bytes
      Max core file size        0                    unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             257066               257066               processes
      Max open files            1024000              1024000              files
      Max locked memory         67108864             67108864             bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       257066               257066               signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Max realtime timeout      unlimited            unlimited            us
      Core pattern: core
       
      2020-10-15 19:41:14 0 [Note] InnoDB: Using Linux native AIO
      2020-10-15 19:41:14 0 [Note] InnoDB: Uses event mutexes
      2020-10-15 19:41:14 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2020-10-15 19:41:14 0 [Note] InnoDB: Number of pools: 1
      2020-10-15 19:41:14 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
      

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              wxiaoguang Xiaoguang Wang
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.