Apache Solr Reference Guide Covering Apache Solr 6.0

Solr process PID running on port 8983
{
"version":"5.0.0 - ubuntu - 2014-12-17 19:36:58",
"startTime":"2014-12-19T19:25:46.853Z",
"uptime":"0 days, 0 hours, 0 minutes, 8 seconds",
"memory":"85.4 MB (%17.4) of 490.7 MB"}
If the status command is not successful, look for error messages in /var/solr/logs/solr.log.
Fine tune your production setup
Memory and GC Settings
By default, the bin/solr script sets the maximum Java heap size to 512M (-Xmx512m), which is fine for getting
started with Solr. For production, you’ll want to increase the maximum heap size based on the memory
requirements of your search application; values between 10 and 20 gigabytes are not uncommon for production
servers. When you need to change the memory settings for your Solr server, use the SOLR_JAVA_MEM variable
in the include file, such as:
SOLR_JAVA_MEM="-Xms10g -Xmx10g"
Also, the include file comes with a set of pre-configured Java Garbage Collection settings that have shown to
work well with Solr for a number of different workloads. However, these settings may not work well for your
specific use of Solr. Consequently, you may need to change the GC settings, which should also be done with the
GC_TUNE variable in the /etc/default/solr.in.sh include file. For more information about tuning your
memory and garbage collection settings, see: JVM Settings.
Out-of-Memory Shutdown Hook
The bin/solr script registers the bin/oom_solr.sh script to be called by the JVM if an OutOfMemoryError
occurs. The oom_solr.sh script will issue a kill -9 to the Solr process that experiences the OutOfMemoryE
rror. This behavior is recommended when running in SolrCloud mode so that ZooKeeper is immediately
notified that a node has experienced a non-recoverable error. Take a moment to inspect the contents of the /op
t/solr/bin/oom_solr.sh script so that you are familiar with the actions the script will perform if it is invoked
by the JVM.
SolrCloud
To run Solr in SolrCloud mode, you need to set the ZK_HOST variable in the include file to point to your
ZooKeeper ensemble. Running the embedded ZooKeeper is not supported in production environments. For
instance, if you have a ZooKeeper ensemble hosted on the following three hosts on the default client port 2181
(zk1, zk2, and zk3), then you would set:
ZK_HOST=zk1,zk2,zk3
When the ZK_HOST variable is set, Solr will launch in "cloud" mode.
ZooKeeper chroot
If you're using a ZooKeeper instance that is shared by other systems, it's recommended to isolate the SolrCloud
znode tree using ZooKeeper's chroot support. For instance, to ensure all znodes created by SolrCloud are stored
Apache Solr Reference Guide 6.0
507