Uploaded image for project: 'Percona Server for MySQL'
  1. Percona Server for MySQL
  2. PS-1075

LP #1673112: percona server 5.7 crashes with signal 11 3merge_buffersP10Sort_paramP11st_io_cache in backtrace

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.7.21-20
    • Component/s: None

      Description

      **Reported in Launchpad by Maxim Fedotov last update 09-10-2017 14:10:24

      Server version: 5.7.15-9-log Percona Server (GPL), Release '9', Revision '9f0fd0a'
      uname -a
      Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/Linux

      error log:
      14:12:20 UTC - 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.
      Attempting to collect some information that could help diagnose the problem.
      As this is a crash and something is definitely wrong, the information
      collection process might fail.
      Please help us make Percona Server better by reporting any
      bugs at http://bugs.percona.com/

      key_buffer_size=8388608
      read_buffer_size=131072
      max_used_connections=1
      max_threads=201
      thread_count=2
      connection_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 87813 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f7890000ae0
      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 = 7f78bc313e80 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xe82b4c]
      /usr/sbin/mysqld(handle_fatal_signal+0x479)[0x7973b9]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f79168b6890]
      /usr/sbin/mysqld[0x1277616]
      /usr/sbin/mysqld(ZN11ha_innobase7cmp_refEPKhS1+0x72)[0xf05832]
      /usr/sbin/mysqld(_Z13merge_buffersP10Sort_paramP11st_io_cacheS2_20Bounds_checked_arrayIhEP11Merge_chunkS3_IS5_Ei+0x6af)[0x7e8b8f]
      /usr/sbin/mysqld(_ZN6Unique3getEP5TABLE+0x32b)[0xd0f96b]
      /usr/sbin/mysqld(_ZN19Query_result_delete10do_deletesEv+0x82)[0xdc2762]
      /usr/sbin/mysqld(_ZN19Query_result_delete8send_eofEv+0x42)[0xdc27f2]
      /usr/sbin/mysqld(_ZN4JOIN4execEv+0x56d)[0xc2a88d]
      /usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x238)[0xc9ce58]
      /usr/sbin/mysqld(_ZN20Sql_cmd_delete_multi7executeEP3THD+0x25a)[0xdc23ca]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0xe39)[0xc5aae9]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x625)[0xc60275]
      /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x877)[0xc60b67]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x1b7)[0xc62177]
      /usr/sbin/mysqld(handle_connection+0x2a0)[0xd262f0]
      /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xe9fa44]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f79168af064]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f79148ef62d]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (7f7890005790): DELETE p from parent p JOIN child c ON c.guid = p.guid WHERE c.int = 1167073
      Connection ID (thread ID): 4
      Status: NOT_KILLED

      You may download the Percona Server operations manual by visiting
      http://www.percona.com/software/percona-server/. You may find information
      in the manual which will help you identify the cause of the crash.
      Writing a core file
      Segmentation fault (core dumped)

      How to reproduce:
      As this situation disappears after running OPTIMIZE TABLE or reloading data from backup, I attach xtrabackup archive, on which this issue can be reproduced.

      File is ~300mb size, so i was unable to attach it to bug.
      https://drive.google.com/file/d/0Bxk6L9OXj5-zU0NYRXc5c1lFZFk/view?usp=sharing

      mysql -uroot

      mysql>use filemrirror;
      mysql>START TRANSACTION;
      mysql>DELETE p from parent p JOIN child c ON c.guid = p.guid WHERE c.int = 1167073;
      mysql>ROLLBACK;

        Smart Checklist

          Attachments

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              lpjirasync lpjirasync (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: