On 6/5/2018 11:12 AM, TK Solr wrote: > My client's Solr 6.6 running on a Windows server is mysteriously > crashing without any JVM crash log. No unusual activities recorded in > solr.log. GC log does not indicate the OOM situation. It's a simple > single-core, single node deployment (no solrCloud). It has very light > load. No indexing activities were running near the crash time.
At this time, Solr doesn't have an OOM killer for Windows. Unless you've implemented something yourself, Solr isn't committing suicide because of OOM. A Solr install on Windows that encounters OOM will most likely continue running. Program operation would be completely unpredictable once an OOM occurs, but I would not expect it to actually die. Some OOM errors might be logged in solr.log, but depending on the exact nature of any OOM problem, logging might not actually be possible. > After exhausting all possibilities (suggestions are welcome), I'd like > to recommend to install some monitoring software but I couldn't find > one that works on Windows for a Java based software. (Some I found can > monitor only EXEs. Since all java software shares the same EXE, > java.EXE, those won't work.) Can anyone recommend some? They don't > need to be free but can't be very expensive since it's a very lightly > used Solr system. Perhaps less than $500? Another thing that Solr doesn't currently provide out of the box is a way to install as a service. Probably your best bet is to find a way to install Solr as a service and then use an existing monitoring solution that can tell you whether or not a service is running. The best bet for an easy service install is probably NSSM. It's got a name that some people hate, but a lot of people use it successfully. https://nssm.cc/ I do have plans to provide a service install for Windows out of the box, but it's part of a larger effort that isn't going to be simple to implement, and I don't expect it to be available for end users until at least Solr version 8.0, possibly even later than that. Regarding the crash problem you've mentioned: If you can't find any information in solr.log about exactly what happened, a heap-related OOM could be possible. The only way to be sure is to try increasing the heap and see whether the situation changes at all. There's no way I can tell you exactly how much heap you'll need -- that's going to require experimentation. https://wiki.apache.org/solr/SolrPerformanceProblems#How_much_heap_space_do_I_need.3F You mentioned looking at a GC log. Can you provide that entire log for analysis? You'll need to use a file-sharing website, attachments are removed by the mailing list. Dropbox tends to be a good choice. Thanks, Shawn
