[MDEV-12344] Crash after kill of first hanged SHOW STATUS query Created: 2017-03-23 Updated: 2023-03-07 Resolved: 2019-05-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Replication |
| Affects Version/s: | 10.1.22 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Ján Regeš | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Incomplete | Votes: | 1 |
| Labels: | Galera, crash, status | ||
| Environment: |
Gentoo, kernel 4.4.6, 8x Intel Xeon E5-2643 0 @ 3.30GHz, 8GB RAM, 3 Galera nodes on the same stable network (no geo-replication) |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Hi, we have Galera cluster based on 3 nodes, each with latest MariaDB 10.1.22. Today morning, one node hangs/locked on query `SHOW STATUS LIKE 'wsrep_local_state'. The same issue I've already reported 5 months ago (still unresolved issue): https://jira.mariadb.org/browse/MDEV-11312 I attach full processlist from hanged time. In this time, i killed first/oldest hanged process with ID 109921. After that, mysqld crashed immediately (i attached error log). There was no query present in an error log. At the end, there is few rows logged after my manual MySQL start. Maybe, it is related to libjemalloc. Server has 8 GB RAM and only 2 GB are allocated, so free memory is not a problem. Thank you for your help. It's really big issue for us. Galera is not stable already for 5 months and there is only 1 relatively small database with only 20-100 req/s. Nodes are on the same stable network with latency about ~0.3ms. Processlist
Error log
|
| Comments |
| Comment by Steve Ruby [ 2017-07-03 ] |
|
I am seeing something similar with these hanged queries that are in the state of "filling schema table" I'm 10.2.6 on Windows server 2008 R2. This issue only started after an upgrade from 10.1.22 TO 10.2.6 I'm not running Galera . the server hangs on several queries like "SHOW STATUS" killing the server has twice resulted in data innodb corruption and having rebuild the server with > 350GB of database is VERY time consuming. I am seeing similar error log entries which include the message "This could be because you hit a bug. It is also possible that this binary |
| Comment by Vladislav Vaintroub [ 2017-07-03 ] |
|
stever, maybe you can attach the error log, and the mysqld.dmp from the crash. It maybe something else mostly likely, but Windows does not have any galera |
| Comment by Jan Lindström (Inactive) [ 2019-05-20 ] |
|
No feedback provided. |
| Comment by Gordan Bobic [ 2023-03-07 ] |