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

Crash (signal 11) on ALTER TABLE ADD PARTITION

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.1.16, 10.1.17
    • 10.1.18
    • None
    • LSB Version: :core-4.1-amd64:core-4.1-noarch
      Distributor ID: CentOS
      Description: CentOS Linux release 7.2.1511 (Core)
      Release: 7.2.1511
      Codename: Core

    Description

      Occasional crash during nightly partition rotation job.
      2-node galera cluster.

      Was not able to correlate to an existing bug report.

      Error log:

      161005  3:00:03 [ERROR] mysqld got signal 11 ;
      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.1.17-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=32
      max_threads=153
      thread_count=22
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467121 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f1dcd8a6008
      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 = 0x7f1efa2d5130 thread_stack 0x48400
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f1f0a0f3ebe]
      /usr/sbin/mysqld(handle_fatal_signal+0x2d5)[0x7f1f09c1a915]
      /lib64/libpthread.so.0(+0xf100)[0x7f1f09238100]
      /usr/sbin/mysqld(_Z20ha_abort_transactionP3THDS0_c+0xa3)[0x7f1f09c25653]
      /usr/sbin/mysqld(_Z15wsrep_abort_thdPvS_c+0x139)[0x7f1f09bcbf39]
      /usr/sbin/mysqld(_Z25wsrep_grant_mdl_exceptionP11MDL_contextP10MDL_ticketPK7MDL_key+0x2a7)[0x7f1f09bbc937]
      /usr/sbin/mysqld(_ZNK8MDL_lock14can_grant_lockE13enum_mdl_typeP11MDL_contextb+0x11f)[0x7f1f09b70e8f]
      /usr/sbin/mysqld(_ZN11MDL_context21try_acquire_lock_implEP11MDL_requestPP10MDL_ticket+0xf1)[0x7f1f09b71b11]
      /usr/sbin/mysqld(_ZN11MDL_context12acquire_lockEP11MDL_requestd+0x2e)[0x7f1f09b7207e]
      /usr/sbin/mysqld(_ZN11MDL_context19upgrade_shared_lockEP10MDL_ticket13enum_mdl_typed+0xae)[0x7f1f09b72d6e]
      /usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x1304)[0x7f1f09b24c14]
      /usr/sbin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x61a)[0x7f1f09b6bd4a]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1206)[0x7f1f09a96356]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28e)[0x7f1f09a9e9be]
      /usr/sbin/mysqld(+0x4361c9)[0x7f1f09a9f1c9]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1fb0)[0x7f1f09aa1850]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x169)[0x7f1f09aa26f9]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x18a)[0x7f1f09b6901a]
      /usr/sbin/mysqld(handle_one_connection+0x40)[0x7f1f09b691f0]
      /lib64/libpthread.so.0(+0x7dc5)[0x7f1f09230dc5]
      /lib64/libc.so.6(clone+0x6d)[0x7f1f07652ced]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f1f03a68020): ALTER TABLE zabbix.history_uint ADD PARTITION (PARTITION p2016_10_15 VALUES less than (UNIX_TIMESTAMP("2016-10-16") div 1))
      Connection ID (thread ID): 214035
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off
       
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      

      Attachments

        Activity

          guzzijason Jason Tucker added a comment -

          server.cnf:

          #
          # These groups are read by MariaDB server.
          # Use it for options that only the server (but not clients) should see
          #
          # See the examples of server my.cnf files in /usr/share/mysql/
          #
           
          # this is read by the standalone daemon and embedded servers
          [server]
           
          # this is only for the mysqld standalone daemon
          [mysqld]
          log_error
           
          #
          # * Galera-related settings
          #
          [galera]
          wsrep_cluster_name="zabbix_cluster"
          datadir=/data1/zabbix-data
          innodb_buffer_pool_size=4G
          innodb_buffer_pool_instances=4
          tmp_table_size=512M
          max_heap_table_size=512M
          # Mandatory settings
          wsrep_on=ON
          wsrep_provider=/usr/lib64/galera/libgalera_smm.so
          wsrep_cluster_address=gcomm://10.0.0.5,10.0.0.6
          binlog_format=row
          default_storage_engine=InnoDB
          innodb_autoinc_lock_mode=2
          #
          # Allow server to accept connections on all interfaces.
          #
          bind-address=0.0.0.0
          #
          # Optional setting
          #wsrep_slave_threads=1
          innodb_flush_log_at_trx_commit=0
           
          # this is only for embedded server
          [embedded]
           
          # This group is only read by MariaDB servers, not by MySQL.
          # If you use the same .cnf file for MySQL and MariaDB,
          # you can put MariaDB-only options here
          [mariadb]
           
          # This group is only read by MariaDB-10.1 servers.
          # If you use the same .cnf file for MariaDB of different versions,
          # use this group for options that older servers don't understand
          [mariadb-10.1]
          

          guzzijason Jason Tucker added a comment - server.cnf: # # These groups are read by MariaDB server. # Use it for options that only the server (but not clients) should see # # See the examples of server my.cnf files in /usr/share/mysql/ #   # this is read by the standalone daemon and embedded servers [server]   # this is only for the mysqld standalone daemon [mysqld] log_error   # # * Galera-related settings # [galera] wsrep_cluster_name="zabbix_cluster" datadir=/data1/zabbix-data innodb_buffer_pool_size=4G innodb_buffer_pool_instances=4 tmp_table_size=512M max_heap_table_size=512M # Mandatory settings wsrep_on=ON wsrep_provider=/usr/lib64/galera/libgalera_smm.so wsrep_cluster_address=gcomm://10.0.0.5,10.0.0.6 binlog_format=row default_storage_engine=InnoDB innodb_autoinc_lock_mode=2 # # Allow server to accept connections on all interfaces. # bind-address=0.0.0.0 # # Optional setting #wsrep_slave_threads=1 innodb_flush_log_at_trx_commit=0   # this is only for embedded server [embedded]   # This group is only read by MariaDB servers, not by MySQL. # If you use the same .cnf file for MySQL and MariaDB, # you can put MariaDB-only options here [mariadb]   # This group is only read by MariaDB-10.1 servers. # If you use the same .cnf file for MariaDB of different versions, # use this group for options that older servers don't understand [mariadb-10.1]
          guzzijason Jason Tucker added a comment -

          Just realized that 10.1.18 was released recently. One of the fixes in that (MDEV-9416) sounds somewhat similar to my issue, although I'm not sure if it's the same or not. At any rate, I will update to 10.1.18 and see if the problem returns. Unfortunately, the problem did not happen consistently - only occasionally, so it may take time to determine if there is any change in stability.

          guzzijason Jason Tucker added a comment - Just realized that 10.1.18 was released recently. One of the fixes in that ( MDEV-9416 ) sounds somewhat similar to my issue, although I'm not sure if it's the same or not. At any rate, I will update to 10.1.18 and see if the problem returns. Unfortunately, the problem did not happen consistently - only occasionally, so it may take time to determine if there is any change in stability.
          guzzijason Jason Tucker added a comment -

          No recurrences of the problem so far. Will monitor for a bit longer before suggesting the this case be closed.

          guzzijason Jason Tucker added a comment - No recurrences of the problem so far. Will monitor for a bit longer before suggesting the this case be closed.
          guzzijason Jason Tucker added a comment -

          It's been nearly a month with no recurrences. I think this issue can be closed at this point.

          guzzijason Jason Tucker added a comment - It's been nearly a month with no recurrences. I think this issue can be closed at this point.

          Thanks for the update. For now, I will close the issue as fixed along with MDEV-9416. Please feel free to comment if it happens again.

          elenst Elena Stepanova added a comment - Thanks for the update. For now, I will close the issue as fixed along with MDEV-9416 . Please feel free to comment if it happens again.

          People

            Unassigned Unassigned
            guzzijason Jason Tucker
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.