Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.5, 10.5.8, 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
Description
MariaDB table_open_cache generates same and excessive number of advisory /proc/locks that causes OTHER programs on machine to waste cpu power ("sys load") when checking for locks. Are those really needed/worth it?
Executing lsof command while there are 100k locks in /proc/locks (made by mariadb with table_open_cache=100k) takes 2 minutes.
I see huge decrease in "sys" load after reducing table_open_cache from 100k to 4k on graphs.
Attachments
Issue Links
- causes
-
MDEV-28495 Corruption due to attempting to start up multiple servers on the same data
- Closed
-
MDEV-28662 [ERROR] mysqld got signal 11 after updating from 10.4.8 to 10.4.24
- Closed
-
MDEV-28697 One Node crashed and did not recover
- Closed
-
MDEV-28976 InnoDB: Missing FILE_CHECKPOINT
- Closed
- relates to
-
MDEV-31568 innodb protection against dual processes accessing data insufficient
- Closed
- links to