-
Notifications
You must be signed in to change notification settings - Fork 0
ESGF_Best_Practices
This document collects some of the recommended best practices for configuring and operating an ESGF Node.
-
Run Tomcat with extended memory, if available. Tomcat settings can be configured by inserting the following lines in the file /etc/esg.env:
- export JAVA_OPTS='-Xmx2048m -Xms1024m -XX:MaxPermSize=1024m'
-
Run Tomcat with SSL debug turned on, but only when trying to solve a security issue, otherwise the output is too verbose. In file /etc/esg.env:
- export CATALINA_OPTS=-Djavax.net.debug=ssl
-
Run Jetty (the Solr container) with extended memory, if available. For example, insert the following line in the file /etc/esg.env:
-
export SOLR_JAVA_OPTS='-Xmx1024m -Xms512m -XX:MaxPermSize=512m'
-
export SOLR_JAVA_OPTS_='-Xmx1024m -Xms512m -XX:MaxPermSize=512m' (options for additional solr instances eg. a "super-noded" instance)
-
-
Optimizing Solr indexes:
-
Run a cron job (for example, once every night) to optimize the Solr index, to increase search performance.
-
Use the esg-node script with the --optimize-index option - will optimized all configured shards' cores.
%> esg-node --optimize-index
-
OR
- Use the following is an example script that can be run as cron to optimize all Solr cores (in the following example: those cores serviced on localhost port 8984)
-
curl -s http://localhost:8984/solr/files/update?commit=true -H "Content-Type:text/xml" --data-binary '' curl -s http://localhost:8984/solr/aggregations/update?commit=true -H "Content-Type:text/xml" --data-binary ''
curl -s http://localhost:8984/solr/datasets/update?commit=true -H "Content-Type:text/xml" --data-binary '<optimize/>'