Error: runtime: VirtualAlloc of [X] bytes failed with errno=1455, fatal error: out of memory when restoring MongoDB

[KenL]

Error: runtime: VirtualAlloc of [X] bytes failed with errno=1455, fatal error: out of memory when restoring MongoDB

 

Environment Details

 

When restoring the MongoDB in Server, the following error may be encounted in the 'mongoRestore.log' file located in the restored MongoDB folder:
 

runtime: VirtualAlloc of [X] bytes failed with errno=1455
fatal error: out of memory

 

• Alteryx Server
  • Version 2021.3.6+
• Embedded MongoDB

Cause

 

During the MongoDB restore process, the machine's memory is exhausted so the process did not complete successfully.

Resolution

 

1. On the Server Controller, click Start > Run and then type 'sysdm.cpl' and press Enter to open the System Properties window.
2. Select the Advanced tab, then under Performance, select Settings...
   image.png
3. Select the Advanced tab, then under Virtual memory, select Change...
   image.png
4. Clear the 'Automatically manage paging file size for all drives' option if checked.
5. Select the drive that contains the paging file. This is typically the C:\ drive.
6. Select Custom size, then increase the Initial size and Maximum size values. A value of up to 40000MB may be required.
7. Click Set then click OK. There will be a prompt to restart the machine before the changes can take effect, so please follow that.
   image.png
8. After restarting the machine, start over the MongoDB restore process. Restore to a new, empty MongoDB folder.

Additional Resources

• MongoDB Backup and Restore
• Introduction to Page Files - Microsoft

[JonathanAllenby]

Quick question on this!
Is there a way to estimate the required size of the paging file?

I figure this may be possible if you know the [x] value from the error message and/or know the size of the MongoDB?

[KenL]

Hi @JonathanAllenby ,

I don't have a way of estimating the required size of the paging file. We see that setting a paging file size of 40 GB (40,000 MB) generally works. If the MongoDB folder is very large in size, it may be prudent to attempt to reduce the size by doing the following:

1. Set Persistence Options in Alteryx System Settings
2. Run a MongoDB backup and restore according to this KB article to reduce the MongoDB folder size

Thanks,

Ken

[JonathanAllenby]

Thanks for the advice!

I did think it was a bit of a stretch to get an exact calculation but this alone is incredibly useful.