XtraDB Cluster crashes when creating temp files for temp table

[Andrew Rampling]

Operating System: Debian Linux 7.8 (wheezy)
Kernel Version: 3.2.0-4-amd64
'innodb_version', '5.6.22-72.0'
'protocol_version', '10'
'slave_type_conversions', ''
'version', '5.6.22-72.0-56-log'
'version_comment', 'Percona XtraDB Cluster (GPL), Release rel72.0, Revision 978, WSREP version 25.8, wsrep_25.8.r4150'
'version_compile_machine', 'x86_64'
'version_compile_os', 'debian-linux-gnu'

MySQL error log output:

2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_2.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_0.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_0.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_0.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_1.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_6.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
01:01:09 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.
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=16777216
read_buffer_size=131072
max_used_connections=1364
max_threads=1502
thread_count=790
connection_count=788
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 615948 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fd69ba48220
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...
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_0.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_1.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:09 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_1.MYI'; try to repair it
2017-06-13 11:01:09 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:10 12982 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_32b6_1.MYI'; try to repair it
2017-06-13 11:01:10 12982 [ERROR] Got an error from unknown thread, /mnt/workspace/percona-xtradb-cluster-5.6-debian-binary-bzr/label_exp/debian-wheezy-x64/percona-xtradb-cluster-5.6-5.6.22-25.8/storage/myisam/mi_write.c:223
2017-06-13 11:01:10 7fd71012a700 InnoDB: Error: Write to file /tmp/#sql32b6_5bf45d_32b.ibd failed at offset 0.
InnoDB: 65536 bytes should have been written, only 0 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2017-06-13 11:01:10 7fd71012a700 InnoDB: Warning: cannot create table `tmp`.`#sql32b6_5bf45d_32b` because tablespace full
2017-06-13 11:01:10 12982 [ERROR] /usr/sbin/mysqld: The table 'product_search_results' is full
stack_bottom = 7fd6fe019e50 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8ccd9e]
/usr/sbin/mysqld(handle_fatal_signal+0x36c)[0x6828dc]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7fdbf2a720a0]
/usr/sbin/mysqld(mi_extra+0x28)[0xac4478]
/usr/sbin/mysqld(_ZN13QEP_tmp_table8end_sendEv+0x49)[0x6def29]
/usr/sbin/mysqld(_Z13sub_select_opP4JOINP13st_join_tableb+0x37)[0x6da327]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x2fb)[0x6d8f0b]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x265)[0x71e645]
/usr/sbin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x175)[0x71e8f5]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x551f)[0x6fd1cf]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5c8)[0x6fd7f8]
/usr/sbin/mysqld[0x6fd8f2]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1076)[0x6fef36]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x202)[0x6ffbe2]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x2ad)[0x6d11dd]
/usr/sbin/mysqld(handle_one_connection+0x42)[0x6d1262]
/usr/sbin/mysqld(pfs_spawn_thread+0x140)[0xb195d0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7fdbf2a69b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fdbf0d5595d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (8a12000): CREATE TEMPORARY TABLE Product_Search_Results
         SELECT DISTINCT
      Product_Base.Product_id,
      Product_Base.Item_id,
      Product_Base.ItemSearch_id,
      Product_Base.Barcode,
      Product_Base.BarcodeInner,
      Product_Base.Brand,
      Product_Base.Name AS Name,
      IF(Product_Base.Description='' AND Product_Base.Description2='' AND Product_Base.Description3='' AND Product_Base.Description4='','',Product_Base.Description) AS description,
      Product_Base.Description2,
      Product_Base.Description3,
      Product_Base.Description4,
      Product_Base.Title,
      Product_Base.Unit,
      CAST(IF("OFF"="ON", ROUND(Product_Base.UnitsPerPack, 2), ROUND(Product_Base.UnitsPerPack,0) ) AS CHAR) AS UnitsPerPack,
      ROUND(Product_Base.Weight,2),
      ROUND(Product_Base.Height,2),
      ROUND(Product_Base.Width,2),
      ROUND(Product_Base.Depth,2),
      CONCAT(Product_Image.filename, '.',Product_Image.extension,'?r=',UNIX_TIMESTAMP(Product_Image.LastUpdated)) AS ProductImage,
      Prod
Connection ID (thread ID): 6029346
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.
170613 11:01:13 mysqld_safe Number of processes running now: 0
170613 11:01:13 mysqld_safe WSREP: not restarting wsrep node automatically
170613 11:01:13 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

[Krunal Bauskar (krunal-bauskar)]

1. Can you re-try your workload with latest version of PXC. (Since 5.6.22 there are multiple minor/major bug fixes and we haven't seen this error)

2. If error still persist you can share
* configuration
* test-case to reproduce.

[Launchpad Janitor (janitor)]

[Expired for Percona XtraDB Cluster because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1988