the server was crashed while some queries were executed concurrently
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona Server moved to https://jira.percona.com/projects/PS |
Triaged
|
High
|
Unassigned |
Bug Description
i had run the test case(http://
server version: Percona-server 5.5.18
here is part of error log:
12026 120418 14:33:51 - mysqld got signal 11 ;
12027 This could be because you hit a bug. It is also possible that this binary
12028 or one of the libraries it was linked against is corrupt, improperly built,
12029 or misconfigured. This error can also be caused by malfunctioning hardware.
12030 We will try our best to scrape up some info that will hopefully help diagnose
12031 the problem, but since we have already crashed, something is definitely wrong
12032 and this may fail.
12033
12034 key_buffer_
12035 read_buffer_
12036 max_used_
12037 max_threads=1000
12038 thread_count=12
12039 connection_count=12
12040 It is possible that mysqld could use up to
12041 key_buffer_size + (read_buffer_size + sort_buffer_
12042 bytes of memory
12043 Hope that's ok; if not, decrease some variables in the equation.
12044
12045 Thread pointer: 0x7f806008cb70
12046 Attempting backtrace. You can use the following information to find out
12047 where mysqld died. If you see no messages after this, something went
12048 terribly wrong...
12049 stack_bottom = 0x412390f8 thread_stack 0x80000
12050 /u01/ps.
12051 /u01/ps.
12052 /lib64/
12053 /lib64/
12054 /u01/ps.
12055 /u01/ps.
12056 /u01/ps.
12057 /u01/ps.
12058 /u01/ps.
12059 /u01/ps.
12060 /u01/ps.
12061 /u01/ps.
12062 /u01/ps.
12063 /u01/ps.
12064 /u01/ps.
12065 /u01/ps.
12066 /u01/ps.
12067 /u01/ps.
12068 /u01/ps.
12069 /u01/ps.
12070 /u01/ps.
12071 /lib64/
12072 /lib64/
12073
12074 Trying to get some variables.
12075 Some pointers may be invalid and cause the dump to abort.
12076 Query (0x7f80600498c0): select id from information_
12077 Connection ID (thread ID): 300588
12078 Status: NOT_KILLED
12079
12080 The manual page at http://
12081 information that should help you find out what is causing the crash.
Changed in percona-server: | |
status: | New → Confirmed |
Changed in percona-server: | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
The linked upstream bug deals with InnoDB internal deadlocks, is that the correct bug linked?