Bug #117501 MySQL server is not responding when we are running ALTER TABLE
Submitted: 18 Feb 11:55 Modified: 18 Feb 13:26
Reporter: Praveen Kumar B A Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Windows Severity:S3 (Non-critical)
Version:8.0.41 OS:Windows
Assigned to: CPU Architecture:x86

[18 Feb 11:55] Praveen Kumar B A
Description:
MySQL server is not responding when we are running ALTER TABLE. 

We started to face this issue from MySQL 8.0.40 onwards. Prior to that MySQL upgrade & database upgrade it went through fine.

How to repeat:
Step1: Execution of ALTER TABLE sql query fails and the show processlist state contains "Waiting for table metadata lock".

use nsm;
ALTER TABLE nsm.nsm_host ADD COLUMN ConnectorId VARCHAR(500) DEFAULT NULL;

mysql> show processlist;
Id | User            | Host               | db   | Command | Time | State                     		| Info
---|-----------------|--------------------|------|---------|------|-------------------------------	|----------------------------------------------------------------
5  | event_scheduler | localhost          | nsm  | Daemon  | 2374 | Waiting on empty queue    		| NULL
25 | root            | localhost:60317    | nsm  | Sleep   | 243  | Waiting for table metadata lock | ALTER TABLE nsm.nsm_host ADD COLUMN ConnectorId VARCHAR(500) DEFAULT NULL
27 | root            | localhost:60428    | nsm  | Query   | 812  | Waiting for table metadata lock | SELECT * FROM nsm.nsm_host

Step2: Restarting the MySQL service is clearning the metadata lock. 
Step3: Rerunning this Step1, again ending up in the issue.

Faced this issue in the MySQL community server windows v8.0.40 & v8.0.41
[18 Feb 11:56] Praveen Kumar B A
show processlist screenshot

Attachment: show processlist screenshot.jpg (image/jpeg, text), 292.94 KiB.

[18 Feb 13:26] MySQL Verification Team
Hi Mr. Kumar,

Thank you for your bug report.

However, let us inform you about this forum. This forum is intended only to reports with fully repeatable test cases.

Each of those test cases should consist of a set of SQL statements, which we then try to repeat. If we manage to repeat your problem, then we proceed in further processing of the bug report.

We have not received such a test case from you.

Can't repeat.