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

LP #1732252: Percona Server crashes during stop/restart when using userstat=1 and Slave_open_temp_tables > 0

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: On Hold
    • Priority: High
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      **Reported in Launchpad by Francisco Bordenave last update 12-01-2018 08:10:06

      Bug description:
      Performing a clean stop/restart when userstat=1 in a multi-sourced slave causes crashes during shutdown process.

      How to repeat:
      1- Create a multi-sourced slave (tested 1 slave with 2 masters)
      2- Enable userstat.
      3- Stop/Restart instance.

      This the stack reported in error log:
      2017-11-14T10:51:24.747540-08:00 0 [Warning] /usr/sbin/mysqld: Forcing close of thread 6 user: 'test'

      18:51:24 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=17179869184
      read_buffer_size=131072
      max_used_connections=4
      max_threads=601
      thread_count=0
      connection_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17016081 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0
      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 = 0 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xed35ac]
      /usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7a15e1]
      /lib64/libpthread.so.0[0x3f1ae0f7e0]
      /usr/sbin/mysqld(_ZN7handler25update_global_table_statsEv+0x17f)[0x80704f]
      /usr/sbin/mysqld(_Z15close_temporaryP5TABLEbb+0xa6)[0xc53bc6]
      /usr/sbin/mysqld(_ZN14Relay_log_info22close_temporary_tablesEv+0x3b)[0xe9e32b]
      /usr/sbin/mysqld(_Z25delete_slave_info_objectsv+0x136)[0xe88a56]
      /usr/sbin/mysqld(signal_hand+0x4a6)[0x793956]
      /usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0x1208a24]
      /lib64/libpthread.so.0[0x3f1ae07aa1]
      /lib64/libc.so.6(clone+0x6d)[0x3f1aae8aad]
      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.

      Tested with Percona Server 5.7.15 and 5.7.18-15-log.

      Masters are 5.7.18-15-log fwiw.

        Smart Checklist

          Attachments

            Activity

              People

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

                Dates

                • Created:
                  Updated: