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

Server Crash on mysqldump with --single-transaction

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.7.25-31.35
    • Component/s: None
    • Labels:
      None

      Description

      Affected Version: 5.7.24-26
      OS: Debian stretch 9.7
      Bin-logs are off!

      Hi there,

      after upgrading from 5.7.23-23 to 5.7.24-26 the server crashes after using mysqldump with --single-transaction option:

      mysqldump --single-transaction > dump.sql
      mysqldump: Couldn't execute 'START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT */': Lost connection to MySQL server during query (2013)

       

      key_buffer_size=8388608
      read_buffer_size=131072
      max_used_connections=2
      max_threads=8193
      thread_count=34
      connection_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 9565838 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      Thread pointer: 0x7fbae8417000
      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 = 7fce42bbca70 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x5647dd3a37ac]
      /usr/sbin/mysqld(handle_fatal_signal+0x489)[0x5647dcc87bf9]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7fce96d9a0c0]
      /usr/sbin/mysqld(my_b_safe_tell+0x12)[0x5647dd3869d2]
      /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG19raw_get_current_logEP11st_log_info+0x2a)[0x5647dd32a93a]
      /usr/sbin/mysqld(+0xd03010)[0x5647dd332010]
      /usr/sbin/mysqld(+0x6ce19a)[0x5647dccfd19a]
      /usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPPFcS0_P13st_plugin_intPvEijS3_+0x1b7)[0x5647dd188247]
      /usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_+0x1d)[0x5647dd1883dd]
      /usr/sbin/mysqld(_Z28ha_start_consistent_snapshotP3THD+0x182)[0x5647dcd04742]
      /usr/sbin/mysqld(_Z11trans_beginP3THDj+0x290)[0x5647dd212ad0]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x2dea)[0x5647dd15fc8a]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_stateb+0x4b5)[0x5647dd165b15]
      /usr/sbin/mysqld(+0xb36c75)[0x5647dd165c75]
      /usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x1523)[0x5647dd167a73]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x373)[0x5647dd169693]
      /usr/sbin/mysqld(handle_connection+0x388)[0x5647dd231688]
      /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x5647dd3be544]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7494)[0x7fce96d90494]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fce94a43acf]
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (7fbae8425030): is an invalid pointer
      Connection ID (thread ID): 607
      Status: NOT_KILLED
      

       

      Couldn't find any bugs in the current, but some old bug reports for version 5.6:
      https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1353644

      Maybe this has again something to do with the missing binlogs in my case?

      Thank you in advance.

      Dominik

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  kenn.takara Kenn Takara
                  Reporter:
                  domhaas Dominik Haas
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: