On 8/4/2016 8:14 PM, Tim Chen wrote: > Couple of thoughts: 1, If Leader goes down, it should just go down, > like dead down, so other servers can do the election and choose the > new leader. This at least avoids bringing down the whole cluster. Am I > right?
Supplementing what Erick told you: When a typical Java program throws OutOfMemoryError, program behavior is completely unpredictable. There are programming techniques that can be used so that behavior IS predictable, but writing that code can be challenging. Solr 5.x and 6.x, when they are started on a UNIX/Linux system, use a Java option to execute a script when OutOfMemoryError happens. This script kills Solr completely. We are working on adding this capability when running on Windows. > 2, Apparently we should not pushing too many documents to Solr, how do > you guys handle this? Set a limit somewhere? There are exactly two ways to deal with OOME problems: Increase the heap or reduce Solr's memory requirements. The number of documents you push to Solr is unlikely to have a large effect on the amount of memory that Solr requires. Here's some information on this topic: https://wiki.apache.org/solr/SolrPerformanceProblems#Java_Heap Thanks, Shawn
