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

Crash during optimize - InnoDB: Assertion failure in file

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.1.34, 10.3.23, 10.4.17
    • Fix Version/s: 10.3, 10.4
    • Labels:
    • Environment:
       OS: CloudLinux like RHEL - Kernel: 3.10.0-962.3.2.lve1.5.32.el6h.x86_64

      Description

      We run rather large production servers with over hundreds of databases with varying sizes between a few MB and many GB.

      To improve performance we optimize tables periodically with a cron running this command:

      /usr/bin/mysqlcheck --optimize --all-databases --auto-repair
      

      We started noticing problems with crashing MariaDB servers during the optimize using MariaDB 10.1. We already switched to MariaDB 10.3 in the meantime.

      The problem keeps returning almost every optimize with MariaDB 10.3 on our most busy production servers. On less busy servers the problem seems more rare. In a test environments we are unable to reproduce the issue.

      Log:

      2020-09-04 08:10:17 0x7fc16c0b0700  InnoDB: Assertion failure in file /builddir/build/BUILD/mariadb-10.3.23/storage/innobase/row/row0merge.cc line 4492
      InnoDB: Failing assertion: table->get_ref_count() == 0
      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.
      200904  8:10:17 [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.3.23-MariaDB-log-cll-lve
      key_buffer_size=67108864
      read_buffer_size=1048576
      max_used_connections=253
      max_threads=502
      thread_count=49
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1104963 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fc0b0178be8
      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 = 0x7fc16c0afd68 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55f8152d3d5e]
      *** stack smashing detected ***: /usr/sbin/mysqld terminated
      

      Config:

      mysqld would have been started with the following arguments:
      --basedir=/usr --bind-address=:: --binlog_checksum=NONE --binlog_format=STATEMENT --datadir=/var/lib/mysql --expire_logs_days=10 --ft_min_word_len=3 --innodb_buffer_pool_size=256M --innodb_checksum_algorithm=innodb --innodb_doublewrite=0 --innodb_file_format=barracuda --innodb_file_per_table=1 --innodb_large_prefix=ON --innodb_log_file_size=192M --innodb_strict_mode=false --innodb_use_native_aio=0 --join_buffer_size=1M --key_buffer_size=64M --local-infile=1 --log-error=/var/log/mysqld.log --log_warnings=2 --long_query_time=2 --max_allowed_packet=24M --max_binlog_size=100M --max_connections=500 --max_heap_table_size=20M --max_user_connections=100 --myisam_sort_buffer_size=32M --open_files_limit=51200 --pid-file=/var/run/mysqld/mysqld.pid --port=3306 --query_cache_size=32M --read_buffer_size=1M --read_rnd_buffer_size=1M --skip-external-locking --slow_query_log=1 --slow_query_log_file=/var/lib/mysql/slow_query.log --socket=/var/lib/mysql_sock/mysql.sock --sort_buffer_size=1M --sql_mode=NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION --ssl --ssl-cert=/etc/pki/tls/certs/server.fullchain --ssl-key=/etc/pki/tls/private/server.mysql.key --ssl_cipher=TLSv1.2 --symbolic-links=0 --table_cache=2048 --table_definition_cache=2048 --thread_cache_size=8 --thread_stack=256K --tmp_table_size=10M --tmpdir=/var/lib/mysql_tmp --user=mysql 
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              Joriz Joris de Leeuw
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration