Crash on shutdown with userstat_running=1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Critical
|
Unassigned |
Bug Description
XtraDB 10.2 crashes with this stack trace
100719 15:33:54 [Note] Error reading relay log event: slave SQL thread was killed
100719 15:33:54 - 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=500
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.
thd: 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 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
This is slave with userstat_running=1
Related branches
- Percona developers: Pending requested
-
Diff: 448 lines (+63/-94)10 files modifiedi_s_innodb_buffer_pool_pages.patch (+24/-67)
innodb_admin_command_base.patch (+1/-1)
innodb_extra_rseg.patch (+3/-3)
innodb_fix_misc.patch (+13/-0)
innodb_lru_dump_restore.patch (+2/-2)
innodb_show_sys_tables.patch (+2/-2)
innodb_split_buf_pool_mutex.patch (+2/-2)
innodb_stats.patch (+3/-3)
mysql-test.diff (+12/-13)
userstat.patch (+1/-1)
Changed in percona-server: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Oleg Tsarev (tsarev) |
milestone: | none → 5.1-12.0 |
importance: | High → Critical |
Changed in percona-server: | |
status: | Triaged → In Progress |
Changed in percona-server: | |
status: | In Progress → Fix Committed |
Changed in percona-server: | |
status: | Fix Committed → Fix Released |
Need test case for reproduce.
I can't reproduce this bug.