Systemd has an option to restart a service automatically. This is probably the most common solution in cases where solr is run in linux.
In the Kube world, the pod should fail a health check if solr is killed and a new pod would then be created and the same persistent volume (with the index) is attached to the new pod. On Wed, Aug 21, 2024 at 10:07 AM <mw...@iu.edu> wrote: > On Fri, Aug 16, 2024 at 09:05:58PM +0000, mtn search wrote: > > oom_solr.sh is provided by Solr to kill the solr process on OOM and log > > this event. Is it a common practice to then also create supporting > > functionality to automatically restart solr after the kill? > > It makes sense to me, to do so. Here we have it running under Monit, > configured to restart it if it disappears, and to send messages when > doing so in case we get into a restart loop somehow. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > library.indianapolis.iu.edu > -- http://www.needhamsoftware.com (work) https://a.co/d/b2sZLD9 (my fantasy fiction book)
