Bug #113950 MySQL 8.0.30 is stuck due to the processing of a large transaction
Submitted: 10 Feb 2024 23:25 Modified: 16 Feb 2024 9:29
Reporter: Ahmed Habeeb Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:8.0.30 OS:Linux
Assigned to: CPU Architecture:x86

[10 Feb 2024 23:25] Ahmed Habeeb
Description:
MySQL 8.0.30 is stuck due to the processing of a large transaction no matter what SQL statement is executed; MySQL does not respond ERROR 1040 (HY000): Too many connections.

2024-02-10T14:56:56.764240Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139700905162496 has waited at fil0fil.cc line 860 for 447 seconds the semaphore:
Mutex at 0x7f11742c8590, Mutex FIL_SHARD created fil0fil.cc:2013, locked by nobody

2024-02-10T14:56:56.784667Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139697625937664 has waited at trx0sys.h line 627 for 435 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784688Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139699514496768 has waited at trx0sys.h line 627 for 438 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784696Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139700921947904 has waited at lock0priv.h line 1177 for 395 seconds the semaphore:
S-lock on RW-latch at 0x7f11743e43c8 created in file sync0sharded_rw.h line 81
number of readers 0, waiters flag 0, lock_word: 20000000
Last time read locked in file lock0lock.cc line 5988
Last time write locked in file /tmp/workspace/aws-mysql-80-rpm-packages/label/build-rhel-8-amd64/rpmbuild/BUILD/mysql-wsrep-8.0.30-26.11/mysql-wsrep-8.0.30-26.11/storage/innobase/srv/srv0srv.cc line 1427
2024-02-10T14:56:56.784706Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139697600575232 has waited at trx0sys.h line 627 for 439 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784713Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139699474409216 has waited at trx0sys.h line 627 for 435 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784720Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139699457562368 has waited at trx0sys.h line 627 for 438 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784727Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139700740507392 has waited at trx0sys.h line 627 for 435 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784734Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139700930340608 has waited at srv0srv.cc line 1307 for 389 seconds the semaphore:
Mutex at 0x40454a0, Mutex SRV_INNODB_MONITOR created srv0srv.cc:1123, locked by nobody

2024-02-10T14:56:56.784753Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139699451348736 has waited at trx0sys.h line 627 for 438 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784760Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139699515553536 has waited at trx0sys.h line 627 for 438 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784766Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139700731062016 has waited at trx0sys.h line 627 for 435 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784773Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139697624880896 has waited at trx0sys.h line 627 for 435 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784779Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139699467011840 has waited at trx0sys.h line 627 for 436 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784786Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139697633335040 has waited at trx0sys.h line 627 for 438 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

2024-02-10T14:56:56.784792Z 0 [Warning] [MY-012985] [InnoDB] A long semaphore wait:
--Thread 139697632278272 has waited at trx0sys.h line 627 for 439 seconds the semaphore:
Mutex at 0x7f117439a268, Mutex TRX_SYS created trx0sys.cc:689, locked by nobody

InnoDB: ###### Starts InnoDB Monitor for 30 secs to print diagnostic info:
InnoDB: Pending preads 0, pwrites 0
2024-02-10T14:57:02.686451Z 4050679 [Warning] [MY-010288] [Server] Connection attributes of length 568 were truncated (74 bytes lost) for connection 4050679, user ecargo_usr@192.168.221.230 (as ecargo_usr), auth: yes

How to repeat:
An incident I couldn't reproduce.
[16 Feb 2024 9:29] MySQL Verification Team
Hello Ahmed Habeeb,

Thank you for taking the time to report a problem.  Unfortunately you are not using a current version of the product you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with the latest versions(8.0.36), please change the version on this bug report to the version you tested, along with the unaltered server error log, exact steps or test case to reproduce the issue at our and change the status back to "Open".  Again, thank you for your continued support of MySQL.

regards,
Umesh