With beefy machines, one strategy is to create multiple JVMs. For example, if you have one JVM and it hosts 32 replicas, splitting that up to 4 JVMs hosting 8 replicas each. That can allow you to drop down the heap allocated to each.
Managing memory is always "exciting" at scale. If you're sorting, faceting, or grouping on a field that does _not_ have docValues enabled, that can be a major memory hog. If you enable docValues you need to re-index completely BTW... >From there, it's a matter of trying to figure out where the memory is being used and see what can be done about that. Best, Erick On Mon, Apr 2, 2018 at 2:57 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/2/2018 2:43 PM, murugesh karmegam wrote: >> So given all of that wondering is there any options >> like G1 GC tuning ? > > Targeted reply. > > I've put some G1 information out there for Solr. > > https://wiki.apache.org/solr/ShawnHeisey > > Thanks, > Shawn >
