Yes, I recommend this. You can't predict a JVM that has had an OOM - so it's best to neutralize it. We have seen cases where the node was messed up but still advertised as active and good in zk due to OOM's. Behavior after an OOM is undefined.
I was actually going to ask if you were positive you had restarted that node in the other OOM thread, because that sounded similar. Just a straw to grasp for, as I'd guess you are sure you did restart it. - Mark On Apr 24, 2013, at 11:37 AM, Timothy Potter <thelabd...@gmail.com> wrote: > Just verifying that it is also recommended to use the JVM options to > kill on OOM? I vaguely recall a message from Mark about this sometime > ago: > > -XX:OnOutOfMemoryError="kill -9 %p" -XX:+HeapDumpOnOutOfMemoryError > > On Wed, Apr 24, 2013 at 9:13 AM, Mark Miller <markrmil...@gmail.com> wrote: >> >> On Apr 24, 2013, at 4:02 AM, Furkan KAMACI <furkankam...@gmail.com> wrote: >> >>> Lucidworks Solr Guide says that: >>> >>> "If you are using Sun's JVM, add the -server command-line option when you >>> start Solr. This tells the JVM that it should optimize for a long running, >>> server process. If the Java runtime on your system is a JRE, rather than a >>> full JDK distribution (including javac and other development tools), then >>> it is possible that it may not support the -server JVM option" >>> >>> Does any folks using -server parameter? Also what parameters you are using >>> to start up Solr? I mean parallel garbage collector vs.? >> >> Unless you are using 32-bit Windows, you are probably getting the server >> JVM. It's not a bad idea to use -server to be sure - it's certainly >> preferable to -client for Solr. >> >> You should generally use the concurrent low pause garbage collector with >> Solr. >> >> - Mark >>
