[PS5534] InnoDB Stuck With state Enforcing Dict Cache Limit

[ps-5534] innodb stuck with state: enforcing dict cache limit created: 28/mar/19 updated: 23/dec/19 resolved: 26/jun/19 status: done

[PS-5534] InnoDB stuck with "state: enforcing dict cache limit"
Created: 28/Mar/19 Updated: 23/Dec/19 Resolved: 26/Jun/19
Status:
Done
Project:
Percona Server for MySQL
Component/s:
None
Affects Version/s:
5.7.11-4
Fix Version/s:
None
Type:
Bug
Priority:
Medium
Reporter:
Denys Zhdanov
Assignee:
Unassigned
Resolution:
Cannot Reproduce
Votes:
0
Labels:
None
Remaining Estimate:
Not Specified
Time Spent:
Not Specified
Original Estimate:
Not Specified
Attachments:
Text File bug.txt File my.cnf File my.cnf
Description
Really similar to https://bugs.mysql.com/bug.php?id=84424
MySQL master suddenly stops all transactions and main innodb thread
stuck in "enforcing dict cache limit" state.
Innodb status and config are in the attachment.
OS and MySQL reboot is not helping.
Comments
Comment by Denys Zhdanov [ 28/Mar/19 ]
Oops, attached right config, ignore previous one.
Comment by Lalit Choudhary [ 08/Apr/19 ]
Hi Denys,
Thank you for the report.
As suggested in MySQL Bug#84424 could please try the following things.
You have to do several things in order to alleviate the problem:
*
increase the additional memory pool
*
increase total number of file handles available to MySQL
*
increase number of file handles for InnoDB
*
improve performance of the I/O on your operating system
Also, please test this with the latest version Percona
server(5.7.25), 5.7.11-4 is an old version.
If still see the same issue please provide the following details.
Looking at my.cnf it's mysql slave instance having a problem.
1.
tell us more about replication topology you have.
2.
a number of database and table you have.
3.
type of SQL load you running on databases.
4.
For how long InnoDB stuck with "state: enforcing dict cache limit
5.
Do you have any backup run scheduled? If yes then Is it happen
when the backup is running?
Generated at Wed Oct 13 19:33:44 UTC 2021 using Jira
8.5.17#805017-sha1:5dff05e3683c28e524092503a39aa89991117061.