Replication with no tmpdir space and InnoDB as tmp_storage_engine can break
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Confirmed
|
Undecided
|
Unassigned | |||
8.0 |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Description:
This is same as bug #1703346, but is repeatable only if internal_
Stack trace is also different:
2017-10-
mysqld: /home/sveta/
11:43:12 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.
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.
key_buffer_
read_buffer_
max_used_
max_threads=151
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fedb0000be0
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 = 7fee18e2dd38 thread_stack 0x46000
/home/sveta/
/home/sveta/
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/lib/x86_
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/home/sveta/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fedb0009390): insert into t1 select * from t1
Connection ID (thread ID): 7
Status: NOT_KILLED
The manual page at http://
information that should help you find out what is causing the crash.
Writing a core file
safe_process[
How to repeat:
See bug #72457:
1. Create small fs:
dd if=/dev/zero of=`pwd`/bug64849 bs=1k count=50000
mkdir ./bug64849_data
sudo /sbin/mkfs.ext2 -F `pwd`/bug64849
sudo mount -o loop `pwd`/bug64849 `pwd`/bug64849_data
sudo chown sveta:sveta bug64849_data/
2. Start MTR:
./mtr --start --suite=rpl --mysqld=
3. Connect to master and run following queries:
mysql> set binlog_
Query OK, 0 rows affected (0.00 sec)
mysql> create table t1(f1 text) engine=myisam;
Query OK, 0 rows affected (0.11 sec)
mysql> insert into t1 values(md5(1));
Query OK, 1 row affected (0.00 sec)
mysql> insert into t1 select * from t1;
Query OK, 1 row affected (0.00 sec)
Records: 1 Duplicates: 0 Warnings: 0
...
mysql> insert into t1 select * from t1;
Query OK, 524288 rows affected (6.10 sec)
Records: 524288 Duplicates: 0 Warnings: 0
mysql> insert into t1 select * from t1;
ERROR 2013 (HY000): Lost connection to MySQL server during query
Suggested fix:
Don't crash if binlog_
Sveta, is there an upstream bug report?