| Info |
|---|
Valid from 5.1The documentation below is valid from Datafari v5.1 upwards |
| Warning |
|---|
First of all : Do not underestimate the importance of SWAP memory ! Be sure your SWAP fits the recommandations according to your physical memory ! We recommand to have at least between 1 and 1.5 times recommend a minimium of 1,5 time the amount of RAM as SWAP memory of your RAM. So Note that if you have a server with 32 GB of RAM, the SWAP partition or file must be at least of 32-48 GBserver is properly sized in terms of RAM, you should almost never see any usage of SWAP. This recommended mininum amount is a safety measure in case you end up in scenarii where you push your Datafari to the limit of your physical hardware. |
The stability and performances of Datafari mainly rely on a good RAM management and its proper distribution between its components. Adding more RAM to a Datafari server is completely useless if you don't do not configure it to exploit the available RAM !
You can check the default JVM RAM configuration of Datafari in the Software requirementsCE in monoserver_community_memory.properties
CASE 1: Configuration priori to the first start of your Datafari
Before the first startup start of Datafari, you can modify into in one location place all of the values of RAM that you want to apply for the different components.
This file is into this folder located in : $DATAFARI_HOME/bin/deployUtils/
You need to edit the file corresponding to your installation case, for example if you use community edition are using the Community Edition of Datafari, edit the file monoserver_community_memory.properties.
There is a line of each component, for example if you want to change the amount of RAM for Solr edit the property :
| Code Block |
|---|
SOLRMEMORY=1g |
| Note |
|---|
Your modifications will be taken account only if Datafari |
...
has never been initialized before. |
CASE 2: Configuration in case you had already started your Datafari at least once before
If your Datafari is already initialized, here are the files location and the parameters that allow you to adjust the JVM RAM (excluding SWAP!) consumption by component :
(You need to restart Datafari for the change changes to be applied)
Component | File location | Parameter |
|---|---|---|
Solr | DATAFARI_HOME/solr/bin/solr.in.sh | SOLR_JAVA_MEM (-Xms and -Xmx) |
ManifoldCF | DATAFARI_HOME/mcf/mcf_home/option.env.unix | -Xms and -Xmx |
Tomcat (Main) | DATAFARI_HOME/tomcat/bin/setenv.sh | CATALINA_OPTS (-Xms and -Xmx) |
Tomcat (MCF) | DATAFARI_HOME/tomcat-mcf/bin/setenv.sh | CATALINA_OPTS (-Xms and -Xmx) |
Cassandra | DATAFARI_HOME/cassandra/conf/jvm-server.options | -Xms and -Xmx |
PostgreSQL | DATAFARI_HOME/pgsql/data/postgresql.conf | shared_buffers |
Elasticsearch | DATAFARI_HOME/elk/elasticsearch/config/jvm.options | -Xms and -Xmx |
Logstash | DATAFARI_HOME/elk/logstash/config/jvm.options | -Xms and -Xmx |
Kibana | DATAFARI_HOME/elk/scripts/set-elk-env.sh | NODE_OPTIONS (--max-old-space-size) |
Tika server (Enterprise Edition) | DATAFARI_HOME/tika-server/bin/set-tika-env.sh | TIKA_SPAWN_MEM (-JXms and -JXmx) |
...