[MDEV-29809] MariaDB: node crash and recovery - Semaphore wait has lasted > 600 seconds. We intentionally crash.... - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Incomplete
Affects Version/s: 10.3.27
Fix Version/s: N/A
Component/s: Server, Storage Engine - InnoDB
Labels:
- crash
- lock
- recovery
Environment:
CentOS7.9 ,16C32G2000G,
MariaDB10.3.27

Description

Several days ago,we met a problem a node of MM cluster crashed and then recovery itself.There was a heavy load-in migration task at that time.The related log is in the attachment，11.PNG tells that the server is hanged and crashed raised signal 6. 12.PNG tells the server raised singal 11 and aborting ,that is the reason backtracing file is not generated.13.PNG and 14.PNG tell the informtion when analyzing singal waiting.
If you need any other information to helping solve the problem ,please contact us,thank you!

Attachments

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

14.PNG
6 kB
2022-10-17 05:23
13.PNG
11 kB
2022-10-17 05:23
12.PNG
49 kB
2022-10-17 05:23
11.PNG
9 kB
2022-10-17 05:23

Issue Links

relates to

MDEV-25048 semaphore has too many locks

Closed

Activity

People

Assignee:: Unassigned

Reporter:: Wenwen Jing

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2022-10-17 05:23

Updated:: 2022-11-23 15:57

Resolved:: 2022-11-23 15:57

Git Integration

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