I am not an expert on this but the oom-killer will kill off the process consuming the greatest amount of memory if the machine runs out of memory, and you should see something to that effect in the system log, /var/log/messages I think.
François On Dec 14, 2011, at 2:54 PM, Adolfo Castro Menna wrote: > I think I found the issue. The ubuntu server is running OOM-Killer which > might be sending a SIGINT to the java process, probably because of memory > consumption. > > Thanks, > Adolfo. > > On Wed, Dec 14, 2011 at 12:44 PM, Otis Gospodnetic < > otis_gospodne...@yahoo.com> wrote: > >> Hi, >> >> Solr won't shut down by itself just because it's idle. :) >> You could run it with debugger attached and breakpoint set in the shutdown >> hook you are talking about and see what calls it. >> >> Otis >> ---- >> >> Performance Monitoring SaaS for Solr - >> http://sematext.com/spm/solr-performance-monitoring/index.html >> >> >> >> >>> ________________________________ >>> From: Adolfo Castro Menna <adolfo.castrome...@gmail.com> >>> To: solr-user@lucene.apache.org >>> Sent: Wednesday, December 14, 2011 8:17 AM >>> Subject: Shutdown hook issue >>> >>> Hi All, >>> >>> I'm experiencing some issues with solr. From time to time solr goes down. >>> After checking the logs, I see that it's due to the shutdown hook being >>> triggered. >>> I still don't know why it happens but it seems to be related to solr being >>> idle. Does anyone have any insights? >>> >>> I'm using Ubuntu 10.04.2 LTS and solr 3.1.0 running on Jetty (default >>> configuration). Solr runs in background, so it doesn't seem to be related >>> to a SIGINT unless ubuntu is sending it for some odd reason. >>> >>> Thanks, >>> Adolfo. >>> >>> >>> >>
