Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.5.11
-
None
-
Kubernetes / mariadb official docker image 10.5.11
Data directory mount via NFS
Description
I have had multiple mariadb hang in multiple container. The mariadb data directory is stored on an NFS share.
When this error arrises, the Mariadb server still accept connections, but any write will hang the connection, making the server rapidly useless (Too many connections).
I don't know why this error arrise, it doesn't seem to be related to mariadb itself as the system call is failing, but the error could be better handled as the mariadb server goes unresponsive.
Would it be possible to crash the process instead of hanging ?
That would allow Kubernetes (or any other container / process manager) to restart the process.
Here are the errors :
2021-08-27 21:34:38 0 [ERROR] [FATAL] InnoDB: fdatasync() returned 13
|
210827 21:34:38 [ERROR] mysqld got signal 6 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
|
Server version: 10.5.11-MariaDB-1:10.5.11+maria~focal
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=42
|
max_threads=152
|
thread_count=29
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 465672 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x0
|
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went
|
terribly wrong...
|
stack_bottom = 0x0 thread_stack 0x49000
|
mysqld(my_print_stacktrace+0x32)[0x563413f15e22]
|
mysqld(handle_fatal_signal+0x485)[0x563413968a35]
|
2021-08-27 21:34:38 135638 [ERROR] [FATAL] InnoDB: fdatasync() returned 13
|
210827 21:34:38 [ERROR] mysqld got signal 6 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
|
Server version: 10.5.11-MariaDB-1:10.5.11+maria~focal
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=119
|
max_threads=152
|
thread_count=79
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 465672 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x7f10680008e8
|
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went
|
terribly wrong...
|
stack_bottom = 0x7f1110dabd58 thread_stack 0x49000
|
mysqld(my_print_stacktrace+0x32)[0x5625498fde22]
|
Printing to addr2line failed
|
mysqld(handle_fatal_signal+0x485)[0x562549350a35]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7f1332b353c0]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f133263b18b]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f133261a859]
|
2021-08-27 21:34:38 0 [ERROR] [FATAL] InnoDB: fdatasync() returned 13
|
210827 21:34:38 [ERROR] mysqld got signal 6 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
|
Server version: 10.5.11-MariaDB-1:10.5.11+maria~focal
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=42
|
max_threads=152
|
thread_count=29
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 465672 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x0
|
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went
|
terribly wrong...
|
stack_bottom = 0x0 thread_stack 0x49000
|
mysqld(my_print_stacktrace+0x32)[0x563413f15e22]
|
mysqld(handle_fatal_signal+0x485)[0x563413968a35]
|