Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
11.2.3, 11.4.1
-
None
-
None
-
Rocky Linux release 8.9 (Green Obsidian)
Description
When loading data via LOAD DATA INFILE
to table with ROCKSDB engine I faced a bug
the MariaDB-server runs in nspwan-systemd containter
After crash the server could not be started, mariadb service eats up all memory up to 107Gb and consumes cpu and then hangs. I could not be stopped via systemctl stop mariadb only kill -9 hepls.
Version: '11.2.3-MariaDB' socket: '/vz/shared/mysql.sock' port: 3306 MariaDB Server
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
240319 15:17:58 [ERROR] mysqld got signal 6 ;
Sorry, we probably made a mistake, and this is a bug.
Your assistance in bug reporting will enable us to fix this for the next release.
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: 11.2.3-MariaDB source revision: 79580f4f96fc2547711f674eb8dd514abd312b4a
key_buffer_size=0
read_buffer_size=8388608
max_used_connections=3
max_threads=401
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4117035 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
I test it on 11.4 and 11.2 version both are susceptible