[MDEV-13957] "Out of memory" messages in errorlog Created: 2017-09-29  Updated: 2017-11-05  Resolved: 2017-11-05

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 5.5.41
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Michael Graf Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: OOM, need_feedback
Environment:

Windows Server 2012 R2
Memory 128 GB (more than 100 GB are free)

Attachments: Zip Archive errorlog.zip     File my.ini    

 Description   

There are a lot of "Out of memory" messages in the errorlog.

170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)
 
170918  8:28:56 [ERROR] mysqld.exe: Out of memory (Needed 2093064 bytes)

The server has more than 100 GB of free memory.
How do I know which parameter do I have to adjust in my.ini ?

 Comments   
Comment by Elena Stepanova [ 2017-10-01 ]

migra, 5.5.41 is almost 3-year old, there have been numerous bug fixes, including those related to OOM. Just for example, MDEV-9462 and MDEV-10595 pop up in the search right away, but surely there have been more. I recommend trying to upgrade to the latest 5.5 and check if the problem goes away.

If it keeps happening after upgrade, please try to enable general log, maybe we'll be able to find out which queries cause the problem by matching error log and general log. But it only makes sense on a recent version, please upgrade first.

Generated at Thu Feb 08 08:09:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.