Watch keynotes and sessions from MongoDB.live, our virtual developer conference.

Memory allocation of xxxxx bytes failed: Not enough Space

Hello there,

We’ve encountered a sudden termination of MongoDB,
checked that there was an error message -
“2020-04-03T14:04:10.960+0800 E STORAGE [thread1] WiredTiger (12) [1585893850:957914][5420:140729384308864], file:collection-2-4945547502775328916.wt, eviction-server: memory allocation of 11431936 bytes failed: Not enough space”

Details error log as below:

mongoDB ver: mongoDB 3.2.9
========================================================================================================================================================================================================================================================
2020-04-03T14:04:10.960+0800 E STORAGE  [thread1] WiredTiger (12) [1585893850:957914][5420:140729384308864], file:collection-2-4945547502775328916.wt, eviction-server: memory allocation of 11431936 bytes failed: Not enough space
2020-04-03T14:04:10.960+0800 E STORAGE  [thread1] WiredTiger (12) [1585893850:960911][5420:140729384308864], file:collection-2-4945547502775328916.wt, eviction-server: session unable to allocate a scratch buffer: Not enough space
2020-04-03T14:04:10.960+0800 E STORAGE  [thread1] WiredTiger (12) [1585893850:960911][5420:140729384308864], eviction-server: cache eviction thread error: Not enough space
2020-04-03T14:04:10.960+0800 E STORAGE  [thread1] WiredTiger (-31804) [1585893850:960911][5420:140729384308864], eviction-server: the process must exit and restart: WT_PANIC: WiredTiger library panic
2020-04-03T14:04:10.960+0800 I -        [thread1] Fatal Assertion 28558
2020-04-03T14:04:10.960+0800 I -        [thread1] 
***aborting after fassert() failure
2020-04-03T14:04:10.994+0800 I -        [WTJournalFlusher] Fatal Assertion 28559
2020-04-03T14:04:10.994+0800 I -        [WTJournalFlusher] 
***aborting after fassert() failure
2020-04-03T14:47:36.529+0800 I CONTROL  [main] ***** SERVER RESTARTED *****

Is there any insight can be shared with us?

Hi @Marco_Chou :wave: and welcome to the community forums.

That’s a sign that your system didn’t have enough memory to complete all the tasks that it was trying to do at the time.

Was your system under heavy load at that time? Do you frequently see issues like this? Does this machine only run MongoDB or do you run other applications that would require large memory use?

I see you’re using MongoDB 3.2 which was end of life’d back in October of 2018. Can you upgrade your MongoDB instances to a supported version (MongoDB 3.6+)? If what you ran into was due to a bug in MongoDB chances are it has been fixed in newer versions.

1 Like