Uploaded image for project: 'Percona XtraDB Cluster'
  1. Percona XtraDB Cluster
  2. PXC-2010

LP #1723079: InnoDB: Assertion failure in thread 140079715497728 in file rem0rec.cc line 580

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      **Reported in Launchpad by Thomas VILLENA last update 24-10-2017 06:44:42

      Hi,
      we have a running cluster with 3 nodes. One of the servers crashes this night with following error messages:

      2017-10-12 00:00:17 7f66d9aeb700 InnoDB: Assertion failure in thread 140079715497728 in file rem0rec.cc line 580
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      22:00:17 UTC - 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.
      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.
      Please help us make Percona XtraDB Cluster better by reporting any
      bugs at https://bugs.launchpad.net/percona-xtradb-cluster

      key_buffer_size=536870912
      read_buffer_size=8388608
      max_used_connections=1025
      max_threads=1026
      thread_count=12
      connection_count=10
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 25753926 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f672a84d000
      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 = 7f66d9aeacf8 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8fd375]
      /usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x666264]
      /lib64/libpthread.so.0[0x30d440f710]
      /lib64/libc.so.6(gsignal+0x35)[0x30d4032625]
      /lib64/libc.so.6(abort+0x175)[0x30d4033e05]
      /usr/sbin/mysqld[0x99264f]
      /usr/sbin/mysqld(_Z25wsrep_rec_get_foreign_keyPhPmPKhP12dict_index_tS4_m+0x72)[0x992c62]
      /usr/sbin/mysqld(_Z24wsrep_append_foreign_keyP5trx_tP14dict_foreign_tPKhP12dict_index_tmm+0x3a6)[0x917156]
      /usr/sbin/mysqld[0x9a2853]
      /usr/sbin/mysqld[0x9a6272]
      /usr/sbin/mysqld[0x9ceaae]
      /usr/sbin/mysqld[0x9cf429]
      /usr/sbin/mysqld[0x9d0a51]
      /usr/sbin/mysqld[0x9aefc0]
      /usr/sbin/mysqld[0x9a2ae7]
      /usr/sbin/mysqld[0x9a6272]
      /usr/sbin/mysqld[0x9ceaae]
      /usr/sbin/mysqld[0x9cf429]
      /usr/sbin/mysqld[0x9d0a51]
      /usr/sbin/mysqld[0x9b3c6b]
      /usr/sbin/mysqld[0x91d08f]
      /usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0xad)[0x5a8efd]
      /usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyy+0xd38)[0x842758]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x215e)[0x6ecf6e]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5e8)[0x6f1ab8]
      /usr/sbin/mysqld[0x6f1c57]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1a69)[0x6f4009]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x1eb)[0x6f54fb]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x6bd2cf]
      /usr/sbin/mysqld(handle_one_connection+0x47)[0x6bd4b7]
      /usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xaf978a]
      /lib64/libpthread.so.0[0x30d44079d1]
      /lib64/libc.so.6(clone+0x6d)[0x30d40e88fd]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (7f66d4019010): is an invalid pointer
      Connection ID (thread ID): 314842217
      Status: NOT_KILLED

      You may download the Percona XtraDB Cluster operations manual by visiting
      http://www.percona.com/software/percona-xtradb-cluster/. You may find information
      in the manual which will help you identify the cause of the crash.
      171012 00:00:23 mysqld_safe Number of processes running now: 0
      171012 00:00:23 mysqld_safe WSREP: not restarting wsrep node automatically
      171012 00:00:23 mysqld_safe mysqld from pid file /data/var/lib/mysql/ns-pandb01.nextsourcia.com.pid ended

      Our Perona XtraDB Cluster:

      Percona-XtraDB-Cluster-galera-2-2.12-1.2682.rhel6.x86_64
      Percona-Server-shared-51-5.1.73-rel14.12.624.rhel6.x86_64
      Percona-XtraDB-Cluster-shared-56-5.6.24-25.11.1.el6.x86_64
      Percona-XtraDB-Cluster-client-56-5.6.24-25.11.1.el6.x86_64
      Percona-XtraDB-Cluster-server-56-5.6.24-25.11.1.el6.x86_64

      We don't know why and how it's happended...

      Regards,

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                krunal.bauskar Krunal Bauskar
                Reporter:
                lpjirasync lpjirasync (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: