thread locks itself on btr_search_latch_part
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Undecided
|
Unassigned | ||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
5.5 |
New
|
Undecided
|
Unassigned | ||
5.6 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Percona Server crashes on long wait for a latch:
--Thread 140161830381312 has waited at btr0sea.c line 1203 for 945.00 seconds the semaphore:
X-lock (wait_ex) on RW-latch at 0x123b4b828 'btr_search_
a writer (thread id 140161830381312) has reserved it in mode wait exclusive
number of readers 1, waiters flag 1, lock_word: ffffffffffffffff
Last time read locked in file btr0sea.c line 1105
Last time write locked in file /dev/shm/
Thread 140161830381312 is trying to get a lock on the latch, but it was locked by the same thread before.
Version: Percona Server (GPL), Release rel30.2, Revision 508
| innodb_
| innodb_
Transactions:
---TRANSACTION 1AFDFF402A, ACTIVE 945 sec starting index read
mysql tables in use 1, locked 1
4 lock struct(s), heap size 1248, 1 row lock(s), undo log entries 5
MySQL thread id 4, OS thread handle 0x7f79f9657700, query id 116599319 Updating
update ....
---TRANSACTION 1AFDFF3FE8, ACTIVE 945 sec starting index read
mysql tables in use 12, locked 0
, holds adaptive hash latch
MySQL thread id 332537, OS thread handle 0x7f79f81c6700, query id 116599225 a.b.c.d user Sending data
SELECT ...
Saw this on 5.0.92-87 Today:
--Thread 140274892576512 has waited at btr0sea.c line 1399 for 0.00 seconds the semaphore:
S-lock on RW-latch at 0x14dc0f60 created in file btr0sea.c line 139
a writer (thread id 140274892576512) has reserved it in mode exclusive
number of readers 0, waiters flag 1, lock_word: 0
Last time read locked in file btr0sea.c line 1290
Last time write locked in file btr0sea.c line 516