percona_innodb_kill_idle_trx_locks sporadically fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Stewart Smith | ||
5.1 |
Fix Released
|
High
|
Stewart Smith | ||
5.5 |
Fix Released
|
High
|
Stewart Smith |
Bug Description
_StringException: Text attachment: traceback
------------
Comment: Server [mysqld.1 - pid: 8455, winpid: 8455, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
InnoDB: DEBUG: update_statistics for test/t1.
InnoDB: DEBUG: update_statistics for test/t1.
111010 11:42:12 - 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.
key_buffer_
read_buffer_
max_used_
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
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 = (nil) thread_stack 0x30000
/mnt/workspace/
/mnt/workspace/
[0xb7783400]
/mnt/workspace/
/mnt/workspace/
/lib/tls/
/lib/tls/
The manual page at http://
information that should help you find out what is causing the crash.
Writing a core file
----------SERVER LOG END-------------
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
BEGIN;
SELECT * FROM t1 FOR UPDATE;
a
1
2
3
UPDATE t1 set a=4;
SELECT * FROM t1;
a
4
4
4
DROP TABLE t1;
SET GLOBAL innodb_
SHOW GLOBAL VARIABLES LIKE 'innodb_
Variable_name Value
innodb_
SELECT * FROM INFORMATION_
VARIABLE_NAME VARIABLE_VALUE
INNODB_
Logfile:
CURRENT_TEST: main.percona_
------------
Related branches
- Stewart Smith (community): Approve
-
Diff: 759 lines (+375/-76)8 files modifiedpatches/innodb_buffer_pool_shm.patch (+3/-3)
patches/innodb_deadlock_count.patch (+4/-4)
patches/innodb_extend_slow.patch (+1/-1)
patches/innodb_fake_changes.patch (+183/-35)
patches/innodb_fast_shutdown.patch (+8/-8)
patches/innodb_kill_idle_transaction.patch (+173/-24)
patches/innodb_split_buf_pool_mutex.patch (+1/-1)
patches/series (+2/-0)
- Stewart Smith (community): Approve
-
Diff: 1610 lines (+489/-184)14 files modifiedpatches/innodb_adaptive_hash_index_partitions.patch (+5/-5)
patches/innodb_buffer_pool_pages_i_s.patch (+1/-1)
patches/innodb_buffer_pool_shm.patch (+3/-3)
patches/innodb_deadlock_count.patch (+4/-4)
patches/innodb_fake_changes.patch (+214/-67)
patches/innodb_fast_checksum.patch (+6/-6)
patches/innodb_files_extend.patch (+6/-6)
patches/innodb_fix_misc.patch (+5/-5)
patches/innodb_kill_idle_transaction.patch (+189/-37)
patches/innodb_pass_corrupt_table.patch (+25/-25)
patches/innodb_separate_doublewrite.patch (+11/-11)
patches/innodb_show_status_extend.patch (+13/-13)
patches/mysql-test.diff (+5/-1)
patches/series (+2/-0)
- Stewart Smith (community): Approve
-
Diff: 5083 lines (+686/-687)41 files modifiedMakefile (+1/-1)
patches/innodb_adaptive_hash_index_partitions.patch (+69/-116)
patches/innodb_admin_command_base.patch (+1/-1)
patches/innodb_buffer_pool_pages_i_s.patch (+3/-3)
patches/innodb_buffer_pool_shm.patch (+3/-3)
patches/innodb_deadlock_count.patch (+1/-1)
patches/innodb_dict_size_limit.patch (+10/-10)
patches/innodb_expand_fast_index_creation.patch (+3/-3)
patches/innodb_expand_import.patch (+18/-18)
patches/innodb_extend_slow.patch (+3/-3)
patches/innodb_extra_rseg.patch (+1/-1)
patches/innodb_fake_changes.patch (+44/-43)
patches/innodb_fast_checksum.patch (+5/-5)
patches/innodb_files_extend.patch (+10/-10)
patches/innodb_fix_misc.patch (+22/-22)
patches/innodb_io_patches.patch (+10/-10)
patches/innodb_kill_idle_transaction.patch (+49/-23)
patches/innodb_lru_dump_restore.patch (+8/-8)
patches/innodb_opt_lru_count.patch (+3/-3)
patches/innodb_overwrite_relay_log_info.patch (+5/-5)
patches/innodb_pass_corrupt_table.patch (+129/-129)
patches/innodb_recovery_patches.patch (+3/-3)
patches/innodb_separate_doublewrite.patch (+8/-8)
patches/innodb_show_lock_name.patch (+8/-8)
patches/innodb_show_status.patch (+11/-11)
patches/innodb_show_status_extend.patch (+6/-6)
patches/innodb_show_sys_tables.patch (+4/-4)
patches/innodb_split_buf_pool_mutex.patch (+110/-73)
patches/innodb_stats.patch (+39/-39)
patches/innodb_thread_concurrency_timer_based.patch (+4/-4)
patches/memory_dynamic_rows.patch (+52/-49)
patches/mysql-test.diff (+6/-30)
patches/percona_support.patch (+1/-1)
patches/response_time_distribution.patch (+3/-3)
patches/show_slave_status_nolock.patch (+1/-1)
patches/show_temp.patch (+2/-2)
patches/slow_extended.patch (+7/-7)
patches/sql_no_fcache.patch (+1/-1)
patches/subunit.patch (+1/-1)
patches/userstat.patch (+17/-17)
patches/valgrind_zlib_suppression.patch (+4/-1)
Also in 5.1: e.g. http:// jenkins. percona. com/view/ Releases/ job/percona- server- 5.1-trunk/ lastCompletedBu ild/BUILD_ TYPE=debug- no-Werror, Host=debian6- 32/testReport/ (root)/ main/percona_ innodb_ kill_idle_ trx/
_StringException: Text attachment: traceback
------------
Comment: Server [mysqld.1 - pid: 30471, winpid: 30471, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
Got error 22 when trying to lock mutex at sql_class.cc, line 489
111009 13:02:14 - 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.
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.
key_buffer_ size=1048576 size=131072 connections= 4 size)*max_ threads = 60053 K
read_buffer_
max_used_
max_threads=151
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 workspace/ percona- server- 5.1-trunk/ BUILD_TYPE/ debug-no- Werror/ Host/debian6- 32/Percona- Server- 5.1.59- rel12.9/ sql/mysqld( my_print_ stacktrace+ 0x22) [0x8532f3c] workspace/ percona- server- 5.1-trunk/ BUILD_TYPE/ debug-no- Werror/ Host/debian6- 32/Percona- Server- 5.1.59- rel12.9/ sql/mysqld( handle_ segfault+ 0x25a) [0x81ff7df] cmov/libc. so.6(abort+ 0x182) [0xb7540b82] workspace/ percona- server- 5.1-trunk/ BUILD_TYPE/ debug-no- Werror/ Host/debian6- 32/Percona- Server- 5.1.59- rel12.9/ sql/mysqld( safe_mutex_ lock+0x150) [0x853b72f] workspace/ percona- server- 5.1-trunk/ BUILD_TYPE/ debug-no- Werror/ Host/debian6- 32/Percona- Server- 5.1.59- rel12.9/ sql/mysqld( thd_kill+ 0x35) [0x81f03b5] workspace/ percona- server- 5.1-trunk/ BUILD_TYPE/ debug-no- Werror/ Host/debian6- 32/Percona- Server- 5.1.59- rel12.9/ sql/mysqld( innobase_ thd_kill+ 0x11) [0x83ddb10] workspace/ percona- server- 5.1-trunk/ BUILD_TYPE/ debug-no- Werror/ Host/debian6- 32/Percona- Server- 5.1.59- rel12.9/ sql/mysqld( ) [0x84470e5] cmov/libpthread .so.0(+ 0x5955) [0xb77ee955] cmov/libc. so.6(clone+ 0x5e) [0xb75dee7e] dev.mysql. com/doc/ mysql/en/ crashing. html contains
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 = (nil) thread_stack 0x30000
/home/jenkins/
/home/jenkins/
[0xb780d400]
/lib/i686/
/home/jenkins/
/home/jenkins/
/home/jenkins/
/home/jenkins/
/lib/i686/
/lib/i686/
The manual page at http://
information that should help you find out what is causing the crash.
Writing a core file
----------SERVER LOG END-------------
Logfile: innodb_ kill_idle_ trx
CURRENT_TEST: main.percona_
mysqltest: At line 25: query 'SELECT * FROM t1' failed: 2013: Lost connection to MySQL server at 'reading initial communication packet', system error: 104
The result from queries just before the failure was: KILL_IDLE_ TRANSACTION 0 kill_idle_ transaction= 1;
< snip >
INNODB_
SET GLOBAL innodb_
SHOW GLOBAL VARIABLES LIKE 'innodb_kill_i...