[MDEV-30684] InnoDB: Semaphore wait has lasted > 600 seconds - Jira

Details

Type: Bug
Status: Open (View Workflow)
Priority: Major
Resolution: Unresolved
Affects Version/s: 10.3.27
Fix Version/s: None
Component/s: Storage Engine - InnoDB
Labels:
- innodb
Environment:
Debian Linux 10, RAM 11 Gb

Description

Desde que realizamos el cambio de query_cache_size = 0 se nos está reproduciendo constantemente errores de transacciones, anteriormente la CPU se encontraba constantemente muy alta y se opto por activar la cache para optimizar el rendimiento.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

50-server.cnf
2023-02-19 05:42
5 kB
Ivan
LOG ERROR.txt
2023-02-19 05:42
33 kB
Ivan
my.cnf
2023-02-19 05:42
1 kB
Ivan

Issue Links

is duplicated by

MDEV-24378 Crashes on Semaphore wait > 600 seconds

Closed

Activity

Marko Mäkelä added a comment - 2023-02-20 09:31

Server hangs can best be diagnosed from stack traces of all threads. MariaDB Server 10.3 is soon reaching its end of life. Several InnoDB hangs, such as ~~MDEV-15020~~, have not been fixed in MariaDB Server release series that are older than 10.6.

Marko Mäkelä added a comment - 2023-02-20 09:31 Server hangs can best be diagnosed from stack traces of all threads . MariaDB Server 10.3 is soon reaching its end of life. Several InnoDB hangs, such as MDEV-15020 , have not been fixed in MariaDB Server release series that are older than 10.6.

People

Assignee:: Unassigned

Reporter:: Ivan

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2023-02-19 05:44

Updated:: 2023-02-20 09:31

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.