Errors getting generated on semaphore section

Description

Hello, We are using Percona MySQL version 5.6.47. We want to know that if there are only few DML operations running concurrently  running on server, then also we observe the things getting printed in semaphore section of show engine innodb status. 
One of the examples which it prints in semaphore sections are :

SEMAPHORES
----------
OS WAIT ARRAY INFO: reservation count 25918822302
--Thread 140246624638720 has waited at btr0cur.cc line 599 for 0.0000 seconds the semaphore:
S-lock on RW-latch at 0x7f8e28960990 '&new_index->lock'
a writer (thread id 140246691780352) has reserved it in mode  exclusive
number of readers 0, waiters flag 0, lock_word: 0
Last time read locked in file btr0cur.cc line 599
Last time write locked in file /mnt/workspace/percona-server-5.6-debian-binary-new/label_exp/min-xenial-x64/test/percona-server-5.6-5.6.46-86.2/storage/innobase/btr/btr0cur.cc line 590
--Thread 140246683387648 has waited at btr0cur.cc line 599 for 0.0000 seconds the semaphore:
S-lock on RW-latch at 0x7f8e28960990 '&new_index->lock'
a writer (thread id 140246691780352) has reserved it in mode  exclusive
number of readers 0, waiters flag 0, lock_word: 0
Last time read locked in file btr0cur.cc line 599
Last time write locked in file /mnt/workspace/percona-server-5.6-debian-binary-new/label_exp/min-xenial-x64/test/percona-server-5.6-5.6.46-86.2/storage/innobase/btr/btr0cur.cc line 590
OS WAIT ARRAY INFO: signal count 23411226242
Mutex spin waits 38395329639, rounds 205888014913, OS waits 2848479663
RW-shared spins 24530582298, rounds 570216696287, OS waits 12881944378
RW-excl spins 52397128608, rounds 627952831319, OS waits 9504289799
Spin rounds per wait: 5.36 mutex, 23.25 RW-shared, 11.98 RW-excl.

 

Can you let us know what does this semaphore error means and what can be done to minimize the error ?

Environment

None

Smart Checklist

Activity

Show:

Lalit Choudhary July 6, 2020 at 12:33 PM

Hi

Thank you for the report.

This is not a bug, and you may refer the following link to know more about it,

https://www.percona.com/blog/2019/12/20/contention-in-mysql-innodb-useful-info-from-the-semaphores-section/

The reported behavior is not a result of a bug but improper use of Percona software. However, the Percona bugs database is supposed only to handle bug reports in Percona product, not for providing help. Help for using our products is available on Percona forums at https://www.percona.com/forums/ and via Percona Customers portal at http://customers.percona.com/

Not a Bug

Details

Assignee

Reporter

Components

Affects versions

Priority

Smart Checklist

Created June 5, 2020 at 5:58 AM
Updated March 6, 2024 at 11:06 AM
Resolved July 6, 2020 at 12:34 PM