Differences

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

--- administration:automation [2015/12/14 19:09] – ↷ Page moved from automation to administration:automation demiankatz
+++ administration:automation [2016/05/13 19:39] – [Using cron] demiankatz
@@ Line 40: / Line 40: @@
 === Why restart VuFind? ===
-The main reason to regularly restart the VuFind is to ensure system stability.  Due to the way Java garbage collection works, Solr can eventually run out of memory and stop responding; periodic restarts are an easy way to avoid this problem.  If you want to automatically detect garbage collection problems in a more sophisticated way, you can try this solution suggested by Erik Mitchell:
+The main reason to regularly restart the VuFind is to ensure system stability.  Due to the way Java garbage collection works, Solr can eventually run out of memory and stop responding; periodic restarts are an easy way to avoid this problem.  It is also a good idea to investigate [[administration:performance#java_tuning|Java tuning]] to address the root cause -- but even with a well-tuned system, occasional restarts (such as, on a weekly basis) can help ensure long-term stability.
-.  Modify the JAVA_OPTIONS to include Garbage Collector logging (Xloggc)
-<code>
-JAVA_OPTIONS="-server -Xms1024m -Xmx3800m -XX:+UseParallelGC -XX:NewRatio=5 -Xloggc:/var/log/vufindr/gc.log"
-</code>
-.  Create and cron a script that searches this log for the word Full.  If it finds it, the GC has failed and it is only a matter of time before vufind bonks.
-<code>
-if [[ $(grep -c 'Full' /var/log/vufind/gc.log) != 0 ]];then
-exec /usr/local/vufind/vufind_cron.sh restart >> /home/vufind/cron.log
-fi
-</code>
-(File paths may need to be adjusted to match your own system).
 ==== Using mysqldump ====