Total memory required to run all configured services is exceeding available memory on the box

Document created by nobin on Feb 8, 2016
Version 1Show Document
  • View in full screen mode

Author: Nobin Kuriakose

 

Original Publication Date: April 28, 2015

 

Env:

  • MapR 3.x
  • MapR 2.x

Symptom:

1. mapr-warden service fails to start after upgrading MapR version 2.x to 3.x. The error messages below are seen in /opt/mapr/logs/warden.log:

Total memory required to run all configured services is exceeding available memory on the box. 
Total memory needed: 9124MB where Total node memory is: 7880MB

Root Cause:

MapR takes care of allocating memory among all the installed services on a node based on percentage of available physical memory. When the package is installed and the configure.sh script is run, MapR generates /opt/mapr/conf/warden.conf file that has details about how much percentage of physical memory needs to be allocated for each service. Memory allocation on MapR version 3.x is different from 2.x. MapR version 2.x allocates 20% of available memory to MapR-FS FileServer whereas MapR version 3.x allocates 35% of available memory which creates more available memory requirement on 3.x version   

Solution:

1. Reduce the memory allocation ratio. Edit below parameter in /opt/mapr/conf/warden.conf with less memory (25% for example) and restart 'mapr-warden' service

service.command.mfs.heapsize.percent=25 

2. Increase the physical memory on the node if possible

Attachments

    Outcomes