About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
administration:starting_and_stopping_solr

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
administration:starting_and_stopping_solr [2023/03/10 11:57] – [Linux (systemd) Method] demiankatzadministration:starting_and_stopping_solr [2023/03/10 12:02] – Reduce redundant systemd examples; recommend systemd for limit fix. demiankatz
Line 32: Line 32:
 </code> </code>
  
-This is warning of some default settings that could impact the performance of your Solr instance. On some Linux platforms, this can be addressed by editing the /etc/security/limits.conf file and adding these lines:+This is warning of some default settings that could impact the performance of your Solr instance. They are unlikely to cause problems if you are only using Solr for testing/development, but they should be addressed in production environments. 
 + 
 +The best way to address the errors on Linux platforms using systemd is to start Solr through systemd and ensure that your [[#linux_systemd_method|systemd configuration]] contains appropriate limit values. The [[#linux_systemd_method|systemd example below]] includes appropriate settings to prevent limit warnings. 
 + 
 +On some Linux platforms, if systemd is not available, the problem can be addressed by editing the /etc/security/limits.conf file and adding these lines:
  
 <code> <code>
Line 45: Line 49:
 It may be necessary to log out of your terminal session and log back in for these settings to take effect. It may be necessary to log out of your terminal session and log back in for these settings to take effect.
  
-On Linux platforms using systemd, you may be able to work around the problem with a systemd file like this example (in a file like /etc/systemd/system/vufind.service): 
- 
-<code> 
-[Unit] 
-Description=VuFind Starter 
-After=network.target 
- 
-[Service] 
-Type=forking 
-ExecStart=/bin/sh -l -c '/usr/local/vufind/solr.sh start' -x 
-PIDFile=/usr/local/vufind/solr/vendor/bin/solr-8983.pid 
-User=vufind-user 
-ExecStop=/bin/sh -l -c "/usr/local/vufind/solr.sh stop" -x 
-SuccessExitStatus=0 
-LimitNOFILE=65000 
-LimitNPROC=65000 
- 
-[Install] 
-WantedBy=multi-user.target 
-</code> 
- 
-(Obviously the /usr/local/vufind path and the vufind-user username should be customized to reflect your local needs). 
- 
-Once this is in place, you can use "sudo service vufind start" and "sudo service vufind stop" to start and stop the process, and appropriate limits will be applied. 
 ==== Windows Method ==== ==== Windows Method ====
  
Line 179: Line 159:
 ExecStop=/bin/sh -l -c "/usr/local/vufind/solr.sh stop" -x ExecStop=/bin/sh -l -c "/usr/local/vufind/solr.sh stop" -x
 SuccessExitStatus=0 SuccessExitStatus=0
 +LimitNOFILE=65000
 +LimitNPROC=65000
  
 [Install] [Install]
administration/starting_and_stopping_solr.txt · Last modified: 2023/10/24 13:47 by demiankatz