Bug #102711 | Getting Semaphore wait has lasted > 600 seconds error while using MySql(5.7.31) | ||
---|---|---|---|
Submitted: | 23 Feb 2021 21:40 | Modified: | 25 Feb 2021 6:10 |
Reporter: | Abiel Dereje | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S3 (Non-critical) |
Version: | 5.7.31 | OS: | Windows |
Assigned to: | CPU Architecture: | Other (Intel i5) | |
Tags: | errors |
[23 Feb 2021 21:40]
Abiel Dereje
[24 Feb 2021 13:30]
MySQL Verification Team
Hi Mr. Dereje, Thank you for your bug report. However, this is not a bug. The error that you report in the title is expected behaviour in the situations with high concurrency. The frequency of getting that error depends on the level of concurrency, design of your schemas, design of your transactions and configuration settings. What we can easily conclude from your report is that settings are definitely wrong. You can find out much more about this problem in our Reference Manual. Not a bug.
[25 Feb 2021 6:10]
Abiel Dereje
what do adjustments do you suggest i make to the settings i ask because the mods i made to those values in the description for my config file i've recently reset to the original values and this issue still persists i've looked at the mysql keeps crashing article in the reference manual but most of those workarounds don't apply to me since they require access to the mysql console and i don't have that since the service won't start. Also i notice you mention the schema as a potential issue i know i imported a group of tables into to my database and overwrote a couple of predefined tables in the phpmydadmin database provided by wampserver one of them being this table with this transaction: DROP TABLE IF EXISTS `columns_priv`; CREATE TABLE IF NOT EXISTS `columns_priv` ( `Host` char(60) COLLATE utf8_bin NOT NULL DEFAULT '', `Db` char(64) COLLATE utf8_bin NOT NULL DEFAULT '', `User` char(32) COLLATE utf8_bin NOT NULL DEFAULT '', `Table_name` char(64) COLLATE utf8_bin NOT NULL DEFAULT '', `Column_name` char(64) COLLATE utf8_bin NOT NULL DEFAULT '', `Timestamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, `Column_priv` set('Select','Insert','Update','References') CHARACTER SET utf8 NOT NULL DEFAULT '' ) could this be the issue?
[25 Feb 2021 13:06]
MySQL Verification Team
Hi Mr. Dereje, DDL can not be the issue, unless there are concurrent queries running on the table that is to be dropped. Regarding settings, see our Reference Manual. However, the most frequent cause of the semaphore wait is the design and the implementation of the application that accesses MySQL server.